summaryrefslogtreecommitdiffstats
path: root/content/browser/storage_partition_impl.cc
Commit message (Collapse)AuthorAgeFilesLines
* Refactor browser side navigator.connect code to not use MessagePortService.mek2015-08-071-4/+1
| | | | | | | | | | | | | | | | This is the first step towards unifying client side and service side ServicePort instances, but also removes a layer of abstraction in how connections to services are setup. The abstraction layer will probably later be reintroduced differently. BUG=426458 Committed: https://crrev.com/9b053ed8f7b8893ad0a5a33d31546c70563ddf20 Cr-Commit-Position: refs/heads/master@{#341987} Review URL: https://codereview.chromium.org/1224263007 Cr-Commit-Position: refs/heads/master@{#342374}
* Revert of Refactor browser side navigator.connect code to not use ↵mek2015-08-061-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MessagePortService. (patchset #2 id:60001 of https://codereview.chromium.org/1224263007/ ) Reason for revert: Seems to be crashing on windows. BUG=517281 Original issue's description: > Refactor browser side navigator.connect code to not use MessagePortService. > > This is the first step towards unifying client side and service side ServicePort > instances, but also removes a layer of abstraction in how connections to > services are setup. The abstraction layer will probably later be reintroduced > differently. > > BUG=426458 > > Committed: https://crrev.com/9b053ed8f7b8893ad0a5a33d31546c70563ddf20 > Cr-Commit-Position: refs/heads/master@{#341987} TBR=avi@chromium.org,bsittler@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=426458 Review URL: https://codereview.chromium.org/1278483004 Cr-Commit-Position: refs/heads/master@{#342026}
* Refactor browser side navigator.connect code to not use MessagePortService.mek2015-08-051-4/+1
| | | | | | | | | | | | | This is the first step towards unifying client side and service side ServicePort instances, but also removes a layer of abstraction in how connections to services are setup. The abstraction layer will probably later be reintroduced differently. BUG=426458 Review URL: https://codereview.chromium.org/1224263007 Cr-Commit-Position: refs/heads/master@{#341987}
* Delete stashed message port implementation from content.mek2015-07-221-15/+2
| | | | | | | | | | | | | | | It's not entirely clear what the future of navigator.connect is, but stashed ports is definitely not it. [1/3] https://codereview.chromium.org/1248003003, deleting most of the blink side of the code [2/3] This patch, deletes the content side [3/3] https://codereview.chromium.org/1248893003, deletes the rest of the blink code BUG=483108 Review URL: https://codereview.chromium.org/1248763005 Cr-Commit-Position: refs/heads/master@{#339919}
* content: Remove use of MessageLoopProxy and deprecated MessageLoop APIsskyostil2015-06-051-2/+6
| | | | | | | | | | | | | | | This patch was mostly autogenerated with https://codereview.chromium.org/1010073002/. BUG=465354 TBR=nick@chromium.org Committed: https://crrev.com/422456f9d53f0bf936a64f21a1463fd0abd3df84 Cr-Commit-Position: refs/heads/master@{#333081} Review URL: https://codereview.chromium.org/1159623009 Cr-Commit-Position: refs/heads/master@{#333112}
* Revert "content: Remove use of MessageLoopProxy and deprecated MessageLoop APIs"skyostil2015-06-051-6/+2
| | | | | | | | | | | | | This reverts commit 422456f9d53f0bf936a64f21a1463fd0abd3df84. TBR=zea@chromium.org BUG=465354 NOTRY=true NOTREECHECKS=true Review URL: https://codereview.chromium.org/1170623003 Cr-Commit-Position: refs/heads/master@{#333086}
* content: Remove use of MessageLoopProxy and deprecated MessageLoop APIsskyostil2015-06-051-2/+6
| | | | | | | | | | | | This patch was mostly autogenerated with https://codereview.chromium.org/1010073002/. BUG=465354 TBR=nick@chromium.org Review URL: https://codereview.chromium.org/1159623009 Cr-Commit-Position: refs/heads/master@{#333081}
* Revert "content: Remove use of MessageLoopProxy and deprecated MessageLoop APIs"skyostil2015-06-051-6/+2
| | | | | | | | | | | | | | | This reverts commit 5d18b2493af36d77d3c491854e3d56f46f5f747c. Reason: Broke iOS build: http://build.chromium.org/p/chromium.mac/builders/iOS_Simulator_%28dbg%29/builds/27843 NOTRY=true NOTREECHECKS=true BUG=465354 TBR=sievers@chromium.org,nick@chromium.org Review URL: https://codereview.chromium.org/1153503009 Cr-Commit-Position: refs/heads/master@{#333047}
* content: Remove use of MessageLoopProxy and deprecated MessageLoop APIsskyostil2015-06-051-2/+6
| | | | | | | | | | | | This patch was mostly autogenerated with https://codereview.chromium.org/1010073002/. BUG=465354 TBR=nick@chromium.org Review URL: https://codereview.chromium.org/1159623009 Cr-Commit-Position: refs/heads/master@{#333043}
* Initial implementation of stashed message ports, content sidemek2015-05-201-2/+15
| | | | | | | | | | | | | | | | | This is part of a series of patches to implement an initial version of a mechanism for a MessagePort to outlive a service worker as described in https://github.com/mkruisselbrink/navigator-connect/blob/gh-pages/docs/api-idea.md#persisted-messageports [1/3] https://codereview.chromium.org/1008533005/, blink side implementation [2/3] this patch, content side implementation [3/3] https://codereview.chromium.org/1063533002/, layout tests BUG=426458, 483108 Review URL: https://codereview.chromium.org/1110103003 Cr-Commit-Position: refs/heads/master@{#330766}
* Beginnings of synchronizing notifications in the notification database.peter2015-05-191-1/+2
| | | | | | | | | | | | | | | | | | For both desktop Chrome and Android we need to support a mechanism for synchronizing open notifications. For desktop the most important case is where Chrome just started up, where there won't be any notifications since the message center is owned by Chrome. For Android, there are more cases, since the platform hosts displaying the notifications and informs Chrome through Intents of mutations. This patch leaves synchronization there mostly out of scope, while still laying the early groundwork towards supporting this. BUG=442143 Review URL: https://codereview.chromium.org/1127013008 Cr-Commit-Position: refs/heads/master@{#330583}
* localStorage: Flushing unwritten data in Android's ChromiumApplication.cmumford2015-05-071-0/+9
| | | | | | | | | | | | | | | This adds a new StoragePartition::Flush method to flush all unwritten data for the StoragePartition. At present this only flushes the DOMStorageContextImpl - not sure if other storage systems require flushing. Also, included a few headers (as suggested by git cl lint), and fixed a few typos. BUG=479767 Review URL: https://codereview.chromium.org/1126733002 Cr-Commit-Position: refs/heads/master@{#328856}
* [BackgroundSync] Hang the BackgroundSyncManager off of the StoragePartitionjkarlin2015-04-201-3/+16
| | | | | | | | | | | Create the BackgroundSyncManager with each StoragePartition. It requires a context class to wrap the BackgroundSyncManager and create/delete it on the IO thread. BUG=477725 Review URL: https://codereview.chromium.org/1097503004 Cr-Commit-Position: refs/heads/master@{#325893}
* The platform notification context should observe the Service Worker Context.peter2015-03-281-1/+5
| | | | | | | | | | | | | | | | | | When a Service Worker registration gets dropped, all notifications associated with that notification should be removed as well. Two cases which will be addressed in follow-up patches are when the Service Worker database gets wiped, and granting the notification context the ability to close deleted notifications by itself. Design document: http://goo.gl/TciXVp BUG=447628 Review URL: https://codereview.chromium.org/1014703007 Cr-Commit-Position: refs/heads/master@{#322692}
* Decouple Cache Storage messaging from Service Worker/Embedded Workerjsbell2015-03-231-5/+20
| | | | | | | | | | | | | | | | We plan to expose the Cache Storage API independent of Service Worker. Tease the IPC message routing off of Service Worker and Embedded Worker, mirroring the other context-independent storage APIs. With this CL the browser side is independent but the renderer side entry point is still only available to the SW's context. Files have been left in the content/*/service_worker/ directories for now; follow-ups will shorten the names and move them to dedicated directories. BUG=439389 Review URL: https://codereview.chromium.org/992353003 Cr-Commit-Position: refs/heads/master@{#321847}
* Hook the notification database up with the StoragePartition.peter2015-03-181-2/+14
| | | | | | | | | | | | | | | | The storage partition will own the PlatformNotificationContextImpl and creates it on the UI thread. It further makes it available to any user of the StoragePartition, the first of which is the notification message filter (that doesn't actually use it yet). Design document: http://goo.gl/TciXVp BUG=447628 Review URL: https://codereview.chromium.org/1011843002 Cr-Commit-Position: refs/heads/master@{#321130}
* favor DCHECK_CURRENTLY_ON for better logs in content/browser/[q-z]*mostynb2015-03-161-15/+15
| | | | | | | | BUG=466848 Review URL: https://codereview.chromium.org/1005683003 Cr-Commit-Position: refs/heads/master@{#320804}
* Refactor navigator.connect code to make it more flexible.mek2015-01-271-5/+9
| | | | | | | | | | | | | | | | | This separates out all the service worker specific code from the generic connection handling. As well as exposing some API in content/public so code outside of content/ can handle connections. This is the first step in making it possible to have chrome extensions, or other code outside of content/ be the endpoint of a connection. This doesn't change any functionality, it just moves code around. BUG=426458 Review URL: https://codereview.chromium.org/861373002 Cr-Commit-Position: refs/heads/master@{#313185}
* Keep track of ServiceWorkerContext's BrowserContext and expose it.mlamouri2015-01-151-5/+15
| | | | | | | | | | | | | This is happening in three steps: 1. StoragePartitionImpl keeps track of its associated BrowserContext. 2. ServiceWorkerContextWrapper keeps track of its associated StoragePartitionImpl. 3. ServiceWorkerContextCore can go up to the BrowserContext. BUG=437151 Review URL: https://codereview.chromium.org/852463002 Cr-Commit-Position: refs/heads/master@{#311681}
* Enable messaging over a navigator.connect initiated channel.mek2014-12-191-14/+19
| | | | | | | | | | | This refactors MessagePortService to decouple it from MessagePortMessageFilter, allowing a new NavigatorConnectContext class to intercept messages sent to a service worker. Layout tests for this are in https://codereview.chromium.org/812853002 BUG=426458 Review URL: https://codereview.chromium.org/785133006 Cr-Commit-Position: refs/heads/master@{#309291}
* Migrate HostZoomMap to live in StoragePartition.wjmaclean2014-11-121-3/+25
| | | | | | | | | | | | | | This CL changes the persistence of host zoom levels to be on a per-storage-partition basis, as opposed to (the current) per-profile basis. This is needed to allow WebView content (withing apps) to keep their zoom levels independent of those in the main browser window. BUG=335317 Review URL: https://codereview.chromium.org/393133002 Cr-Commit-Position: refs/heads/master@{#303841}
* Refactor GeofencingManager to have one instance per StoragePartition.mek2014-10-231-3/+18
| | | | | | | | | | | Add a new GeofencingService class for the few global tasks GeofencingManager used to do. BUG=383125 Review URL: https://codereview.chromium.org/645763003 Cr-Commit-Position: refs/heads/master@{#300960}
* [ServiceWorkerCache] QuotaClientMask should handle kServiceWorkerCacheIDjkarlin2014-10-221-1/+4
| | | | | | | | | | When removing ServiceWorker data with the QuotaClient we should remove both registrations and cache data. This CL adds the cache data id. BUG=420159 Review URL: https://codereview.chromium.org/672433002 Cr-Commit-Position: refs/heads/master@{#300712}
* Added quota client for serviceworker. Enables 'clear past <time> data'.dmurph2014-10-211-1/+2
| | | | | | | | | | | BUG=419287 Committed: https://crrev.com/f6916df879bf23bacf994880359c980f4249e324 Cr-Commit-Position: refs/heads/master@{#299918} Review URL: https://codereview.chromium.org/633273002 Cr-Commit-Position: refs/heads/master@{#300405}
* Revert of Added quota client for serviceworker. Enables 'clear past <time> ↵kareng2014-10-201-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | data'. (patchset #7 id:300001 of https://codereview.chromium.org/633273002/) Reason for revert: causing crashes https://code.google.com/p/chromium/issues/detail?id=424831 Original issue's description: > Added quota client for serviceworker. Enables 'clear past <time> data'. > > BUG=419287 > > Committed: https://crrev.com/f6916df879bf23bacf994880359c980f4249e324 > Cr-Commit-Position: refs/heads/master@{#299918} TBR=michaeln@chromium.org,jsbell@chromium.org,sky@chromium.org,dmurph@chromium.org NOTREECHECKS=true NOTRY=true BUG=419287 Review URL: https://codereview.chromium.org/654323003 Cr-Commit-Position: refs/heads/master@{#300251}
* Added quota client for serviceworker. Enables 'clear past <time> data'.dmurph2014-10-161-1/+2
| | | | | | | | BUG=419287 Review URL: https://codereview.chromium.org/633273002 Cr-Commit-Position: refs/heads/master@{#299918}
* Service Worker: Respect the "clear on exit" content settingfalken2014-10-161-1/+2
| | | | | | | | | | | Now Service Worker registrations and data get deleted as per SpecialStoragePolicy. BUG=419280 Review URL: https://codereview.chromium.org/633873002 Cr-Commit-Position: refs/heads/master@{#299842}
* Remove webkit/browser/, point everything to storage/browser/ insteadpilgrim2014-09-101-2/+2
| | | | | | | | | BUG=338338 TBR=darin@chromium.org Review URL: https://codereview.chromium.org/559063002 Cr-Commit-Position: refs/heads/master@{#294258}
* Remove implicit conversions from scoped_refptr to T* in content/dcheng2014-08-261-3/+9
| | | | | | | | | | | This patch was generated by running the rewrite_scoped_refptr clang tool on a Linux build. BUG=110610 Review URL: https://codereview.chromium.org/504273002 Cr-Commit-Position: refs/heads/master@{#291986}
* Collapse fileapi, webkit_blob, webkit_database, quota, and webkit_common ↵pilgrim@chromium.org2014-08-221-79/+85
| | | | | | | | | | | | | | | | namespaces into single storage namespace As discussed here: https://groups.google.com/a/chromium.org/forum/#!topic/storage-dev/aQall8GOrS4 BUG=338338 TBR=cevans NOTRY=true Review URL: https://codereview.chromium.org/492873002 Cr-Commit-Position: refs/heads/master@{#291485} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291485 0039d316-1c4b-4281-b951-d872f2087c98
* Service Worker: Hook up browsing data deletionjsbell@chromium.org2014-08-111-1/+5
| | | | | | | | | | | | | | | | | | | | | Ensure that chrome://settings/cookies lists origins containing Service Workers and that users can delete the storage. While this is minimally functional, there are several caveats: * A dummy size and timestamp are displayed in the UI, as the actual data is not yet available from the SW context. * Integration with quota remains to be implemented. In particular, UI and extension APIs that allow browsing data to be deleted by date range (e.g. "clear last hour") continue to ignore SW data. * Deletion is done by simply unregistering all SWs in the origin. If unregistration is delayed by an active controllee, the deletion also be (silently) delayed. BUG=388164 Review URL: https://codereview.chromium.org/394063003 Cr-Commit-Position: refs/heads/master@{#288784} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288784 0039d316-1c4b-4281-b951-d872f2087c98
* Fix ExtensionServiceTest.ClearExtensionData flakinessjochen@chromium.org2014-07-311-5/+10
| | | | | | | | | | | | | The test runs work on the IO thread, but doesn't wait for the IO thread. Fails ~17% of the time on ChromeOS BUG=396504 R=ajwong@chromium.org TBR=torne@chromium.org Review URL: https://codereview.chromium.org/421193002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286674 0039d316-1c4b-4281-b951-d872f2087c98
* Use STATIC_CONST_MEMBER_DEFINITION to make constant definitions clearer.pkasting@chromium.org2014-07-111-13/+26
| | | | | | | | | | | This is a followup to http://crrev.com/282419 . BUG=none TEST=none Review URL: https://codereview.chromium.org/383863002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282644 0039d316-1c4b-4281-b951-d872f2087c98
* Fixes for re-enabling more MSVC level 4 warnings: misc edition #1pkasting@chromium.org2014-07-101-0/+15
| | | | | | | | | | | | | | | | This contains fixes for the following sorts of issues: * Signedness mismatch The problem here is that using enums to declare bitmasks results in the enum values being signed, when all consumers want to use the values in an unsigned context. Declaring them as consts allows using the more appropriate uint32 type. In C++11 we could use "enum class" for this, but C++11 isn't legal yet. BUG=81439 TEST=none Review URL: https://codereview.chromium.org/385443002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282419 0039d316-1c4b-4281-b951-d872f2087c98
* Teach EmbeddedWorkerInstance to create a process when it needs one.jyasskin@chromium.org2014-04-291-1/+1
| | | | | | | | | | | | This saves the BrowserContext into the ServiceWorkerContextWrapper, and uses it when no process is available. We always choose a renderer process on the UI thread and take a reference to it before asking the renderer to start the SW thread. This also fixes a race where a process might die before we have a chance to use it. We'll probably need to thread more process IDs through in cases where there might not be a ProviderHost, but that can wait for a subsequent CL. BUG=359811,362060, 362058 Review URL: https://codereview.chromium.org/238043002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266825 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup storage_partition_impl_unittest.cc.ajwong@chromium.org2013-12-281-25/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | Removes: - unnecessary casts - unnecessary conversions to pointers - unnecessary wrapper over RunLoop. It also removes stack-based creation of the StoragePartition and temp directories. This was fragile and unnecessary. The TestBrowserContext itself already created a default one. The stack-based version was actually coopting contexts that were created in the default partition to create a partial stub. This unfortunately also avoided most of the initialization code and checks in the StoragePartitionImpl::Create() function leading to more fragility. Now, each test case only has one default StoragePartition which is correctly tied to the containing BrowserContext. The contexts in this partition are also no longer shared by the stubs. TBR=boliu BUG=none Review URL: https://codereview.chromium.org/101423007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242675 0039d316-1c4b-4281-b951-d872f2087c98
* Move DeleteAllCreatedBetweenForHostAsync to CookieStoresdefresne@chromium.org2013-12-191-2/+2
| | | | | | | | | | | | | | | On iOS, CookieStore is not a CookieMonster and GetCookieMonster() returns NULL. Move DeleteAllCreatedBetweenForHostAsync to CookieStore to allow iOS to provide an implementation. Add implementation for fake / mock implementations. BUG=328059 R=toyoshim@chromium.org, sky@chromium.org, erikwright@chromium.org Review URL: https://codereview.chromium.org/100863008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@241901 0039d316-1c4b-4281-b951-d872f2087c98
* ServiceWorker scaffolding.michaeln@chromium.org2013-11-131-4/+8
| | | | | | | | | | | Refactor the 'context' class to have a thread-safe refcounted wrapper for use by higher level chromium code, and a single-threaded nonrefcounted core for use in the service worker lib. Added explicit Init() and Shutdown() methods on the wrapper class which are used by StoragePartitionImpl to get things started and cleaned up. TBR=jam BUG=285976 Review URL: https://codereview.chromium.org/61023005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234756 0039d316-1c4b-4281-b951-d872f2087c98
* BrowsingDataRemover, (re)use StoragePartition deletion code.lazyboy@chromium.org2013-11-061-149/+248
| | | | | | | | | | | This CL removes code duplication around storage partition related data removal code from BrowsingDataRemover and re-uses StoragePartition::ClearData* method. BUG=180118 Test= Review URL: https://codereview.chromium.org/37843003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233365 0039d316-1c4b-4281-b951-d872f2087c98
* Stub out initial NavigationController browser implementationalecflett@chromium.org2013-09-211-0/+10
| | | | | | | | | | | This is the initial cut for the browser-side NavigationControllerDispatcherHost, and all the various related support plumbing to hook up two initial messages. BUG= 285976 Review URL: https://chromiumcodereview.appspot.com/23615009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224585 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 219709 "Remove the Extensions URLRequestContext."earthdok@chromium.org2013-08-271-28/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reverted due to crashes under memory tools. BUG=280138 > Remove the Extensions URLRequestContext. > > Though chrome-extension: scheme URLs support cookies, they do not share > a namespace with http: and https:. In particular, chrome-extension://a and > http://a should not have the same set of cookies. > > To enforce this, previously the code created a completely separate > URLRequestContext for servicing chrome-extension: schemes. However, > the code really only used this object as a method for conveying the > correct cookie jar from Profile creation to a few spots where cookies > were accessed; the rest of the URLRequestContext functionality was unused. > > This CL removes the Extensions URLRequestContext code and replaces it > with APIs that directly expose the needed net::CookieStore. > > Lastly, CookieMonster::EnableFileScheme() is removed and > CookieMonster::Delegate is renamed CookieMonsterDelegate. > > EnableFileScheme is an inherently racy API because > CookieMonsters are creatable on all threads and this > function sets an unprotected global flag. CookieMonsterDelegate > is preferable to the nested interface because it can now be > forward declared. > > TBRing darin and sky to cover the rest of the mechanical unittest changes. > > TBR=darin,sky > BUG=158386,159193,57884 > > Review URL: https://chromiumcodereview.appspot.com/12546016 TBR=ajwong@chromium.org Review URL: https://codereview.chromium.org/23551005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219787 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the Extensions URLRequestContext.ajwong@chromium.org2013-08-271-53/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Though chrome-extension: scheme URLs support cookies, they do not share a namespace with http: and https:. In particular, chrome-extension://a and http://a should not have the same set of cookies. To enforce this, previously the code created a completely separate URLRequestContext for servicing chrome-extension: schemes. However, the code really only used this object as a method for conveying the correct cookie jar from Profile creation to a few spots where cookies were accessed; the rest of the URLRequestContext functionality was unused. This CL removes the Extensions URLRequestContext code and replaces it with APIs that directly expose the needed net::CookieStore. Lastly, CookieMonster::EnableFileScheme() is removed and CookieMonster::Delegate is renamed CookieMonsterDelegate. EnableFileScheme is an inherently racy API because CookieMonsters are creatable on all threads and this function sets an unprotected global flag. CookieMonsterDelegate is preferable to the nested interface because it can now be forward declared. TBRing darin and sky to cover the rest of the mechanical unittest changes. TBR=darin,sky BUG=158386,159193,57884 Review URL: https://chromiumcodereview.appspot.com/12546016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219709 0039d316-1c4b-4281-b951-d872f2087c98
* Remove unused variable declaration.etienneb@chromium.org2013-08-211-1/+0
| | | | | | | | | | | | This issue was found by a linter. R=sky@chromium.org BUG= Review URL: https://chromiumcodereview.appspot.com/23373002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218761 0039d316-1c4b-4281-b951-d872f2087c98
* Discard FileAPI pending operations on shutdownkinuko@chromium.org2013-08-141-0/+3
| | | | | | | | | | | | | | | Making a few changes to try to discard more operations earlier. - Create SequencedTaskRunner with SKIP_ON_SHUTDOWN shutdown behavior - Call FileSystemContext::Shutdown when StoragePartitionImpl goes away to give earlier notice to discard inflight operations BUG=271903 TEST=tried a few manual shutdown tests with pending operations Review URL: https://chromiumcodereview.appspot.com/22893003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217488 0039d316-1c4b-4281-b951-d872f2087c98
* Adds a SqlLite backend to WebRTCIdentityStore.jiayl@chromium.org2013-08-081-6/+21
| | | | | | | | | | | | | | | | | WebRTCIdentityStore maintains a list of inflight requests. If a new request is identical (i.e. same origin, identity_name, common_name) to a inflight request, the new one is joined into the existing one, so that it will not make duplicated requests to the backend or generate dupicated identities. If the backend does not find an existing identity, WebRTCIdentityStore generates a new one and adds it to the backend. The backend borrows most of the design from SQLiteServerBoundCertStore::Backend. It loads the database into memory on the first find request. Add or delete database operations are batched to commit every 30 seconds or every 512 operations. BUG= Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=216264 Review URL: https://chromiumcodereview.appspot.com/21453002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216448 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 216264 "Adds a SqlLite backend to WebRTCIdentityStore."jyasskin@chromium.org2013-08-071-21/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to fix a memory leak: http://build.chromium.org/p/chromium.memory.fyi/builders/Linux%20Heapcheck/builds/28768/steps/heapcheck%20test%3A%20content/logs/stdio Leak of 160 bytes in 1 objects allocated from: @ 7f1611ba10e0 content::WebRTCIdentityStore::RequestIdentity @ a51510 content::WebRTCIdentityStoreTest_CancelRequest_Test::TestBody Leak of 71 bytes in 1 objects allocated from: @ 7f160f01ca89 std::basic_string::_Rep::_S_create @ 7f161c6a5cac GURL::GURL @ a514de content::WebRTCIdentityStoreTest_CancelRequest_Test::TestBody > Adds a SqlLite backend to WebRTCIdentityStore. > WebRTCIdentityStore maintains a list of inflight requests. If a new request is identical (i.e. same origin, identity_name, common_name) to a inflight request, the new one is joined into the existing one, so that it will not make duplicated requests to the backend or generate dupicated identities. > > If the backend does not find an existing identity, WebRTCIdentityStore generates a new one and adds it to the backend. > > The backend borrows most of the design from SQLiteServerBoundCertStore::Backend. It loads the database into memory on the first find request. Add or delete database operations are batched to commit every 30 seconds or every 512 operations. > > > BUG= > > Review URL: https://chromiumcodereview.appspot.com/21453002 R=jiayl@chromium.org Review URL: https://codereview.chromium.org/22264011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216282 0039d316-1c4b-4281-b951-d872f2087c98
* Adds a SqlLite backend to WebRTCIdentityStore.jiayl@chromium.org2013-08-071-6/+21
| | | | | | | | | | | | | | | WebRTCIdentityStore maintains a list of inflight requests. If a new request is identical (i.e. same origin, identity_name, common_name) to a inflight request, the new one is joined into the existing one, so that it will not make duplicated requests to the backend or generate dupicated identities. If the backend does not find an existing identity, WebRTCIdentityStore generates a new one and adds it to the backend. The backend borrows most of the design from SQLiteServerBoundCertStore::Backend. It loads the database into memory on the first find request. Add or delete database operations are batched to commit every 30 seconds or every 512 operations. BUG= Review URL: https://chromiumcodereview.appspot.com/21453002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216264 0039d316-1c4b-4281-b951-d872f2087c98
* Move webkit/{browser,common}/dom_storage into content/kinuko@chromium.org2013-08-071-13/+15
| | | | | | | | | | | | | | | | | | Mechanical changes only, directory moving + * renamed all DomStorage* to DOMStorage* for consistency * renamed DOMStorageContextImpl to DOMStorageContextProxy, and renamed DomStorageContext to DOMStorageContextImpl * other minor cleanups Diff for dom_storage_context_impl.* may look a bit messy due to chained renames (it's just replaced with former webkit/browser/dom_storage/dom_storage_context.*) BUG=265769 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/22297005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216211 0039d316-1c4b-4281-b951-d872f2087c98
* Storage partition: correctly delete cookie(s) when origin is specified.lazyboy@chromium.org2013-08-071-3/+13
| | | | | | | | | | | | | We were incorrectly removing cookies /w all origins while deleting cookies for a specific origin within a range (storage_partition_impl.cc, ClearCookiesOnIOThread). BUG=180118 Test=MultiThreadedCookieMonsterTest.ThreadCheckDeleteAllCreatedBetweenForHost Review URL: https://chromiumcodereview.appspot.com/20745004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216116 0039d316-1c4b-4281-b951-d872f2087c98
* Rename enum in StoragePartition according to style guide.lazyboy@chromium.org2013-08-021-3/+3
| | | | | | | | | | | | Enums should have ALL_CAPS with enum name as prefix, according to style guide. BUG=None Test=Rename only change. Review URL: https://chromiumcodereview.appspot.com/21646002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215344 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-25 16:17:39 +0000