summaryrefslogtreecommitdiffstats
path: root/ppapi/proxy/websocket_resource.cc
Commit message (Collapse)AuthorAgeFilesLines
* Add PPAPI_BEGIN_MESSAGE_MAP and PPAPI_END_MESSAGE_MAP to be used when ↵jam@chromium.org2014-05-131-2/+2
| | | | | | | | | | | | | dispatching IPCs using PPAPI_DISPATCH_*. This is because the IPC_BEGIN_MESSAGE_MAP macros are closely tied to IPC_MESSAGE_HANDLERS. This is split off from https://codereview.chromium.org/283623002/ BUG=304341 R=brettw@chromium.org, tsepez@chromium.org Review URL: https://codereview.chromium.org/281803003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270218 0039d316-1c4b-4281-b951-d872f2087c98
* Move Blink dependency out of plugin proxy code.bbudge@chromium.org2014-03-181-13/+5
| | | | | | | | | | Moves dependency on WebSocket.h from plugin to host. BUG=350097 Review URL: https://codereview.chromium.org/202143007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257796 0039d316-1c4b-4281-b951-d872f2087c98
* Rename WebKit namespace to blink (part 5)abarth@chromium.org2013-11-071-3/+3
| | | | | | | | | | | | This CL updates all references to the WebKit namespace outside of content, chrome, and components. TBR=darin@chromium.org BUG=295096 Review URL: https://codereview.chromium.org/61553006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233518 0039d316-1c4b-4281-b951-d872f2087c98
* NaCl CompletionCallback is called twice in WebSocket::ReceiveMessage and ↵yhirano@chromium.org2013-07-261-6/+17
| | | | | | | | | | | | | | | | | | crashes the NaCl plugin Some async APIs such as ReceiveMessage takes a completion callback which is called when the operation completes. A completion callback must be called exactly once. If a user calls an async API from non-main message loop, the completion callback will be post to the message loop from the main message loop. But there was no way to detect whether PostRun of the completion callback was called and it caused repetitive calls of PostRun, which leads to an assertion failure and process crash. We fix the issue in this CL. BUG=258018 R=dmichael Review URL: https://chromiumcodereview.appspot.com/19463005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213804 0039d316-1c4b-4281-b951-d872f2087c98
* Update Blink include pathsabarth@chromium.org2013-06-171-1/+1
| | | | | | | | | | | | | This CL changes the majority of include paths from the old Source/WebKit/chromium/public to the new public/web directory. TBR=darin BUG=239545 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/17148003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206664 0039d316-1c4b-4281-b951-d872f2087c98
* Update ppapi/ to use scoped_refptr<T>::get() rather than implicit "operator T*"rsleevi@chromium.org2013-06-021-10/+10
| | | | | | | | | | | Linux fixes BUG=110610 TBR=darin Review URL: https://chromiumcodereview.appspot.com/15806016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203629 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Fix WebSocket Var ref leak receiving binarydmichael@chromium.org2013-02-041-3/+3
| | | | | | | | | | | | | | | | | | | | | | | BUG=173503 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180093 Reopened; was reverted here: https://src.chromium.org/viewvc/chrome?view=rev&revision=180105 Tests were failing because the IRT was not rebuilt due to a gyp problem, which was fixed here: https://src.chromium.org/viewvc/chrome?view=rev&revision=180182 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180190 Reverted again due to 2 tests still failing on Windows 7 and XP: https://src.chromium.org/viewvc/chrome?view=rev&revision=180239 They're failing the new leak check. It's not clear yet if that's a real leak or another build issue; I will investigate separately. This CL still fixes a serious leak on all platforms, so landing without the leak check for now to keep the tests green. Review URL: https://chromiumcodereview.appspot.com/12096099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180428 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 180190dmichael@chromium.org2013-02-021-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Windows tests are still failing: http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%282%29/builds/12476/steps/browser_tests/logs/stdio http://build.chromium.org/p/chromium.win/buildstatus?builder=XP%20Tests%20%28dbg%29%282%29&number=26342 > PPAPI: Fix WebSocket Var ref leak receiving binary > > BUG=173503 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180093 > > Reopened; was reverted here: > https://src.chromium.org/viewvc/chrome?view=rev&revision=180105 > Tests were failing because the IRT was not rebuilt due to a gyp problem, which was fixed here: > https://src.chromium.org/viewvc/chrome?view=rev&revision=180182 > > Review URL: https://codereview.chromium.org/12096099 TBR=dmichael@chromium.org Review URL: https://codereview.chromium.org/12192002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180239 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Fix WebSocket Var ref leak receiving binarydmichael@chromium.org2013-02-011-3/+3
| | | | | | | | | | | | | | | BUG=173503 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180093 Reopened; was reverted here: https://src.chromium.org/viewvc/chrome?view=rev&revision=180105 Tests were failing because the IRT was not rebuilt due to a gyp problem, which was fixed here: https://src.chromium.org/viewvc/chrome?view=rev&revision=180182 Review URL: https://codereview.chromium.org/12096099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180190 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 180093koz@chromium.org2013-02-011-3/+3
| | | | | | | | | | | | | | | | | | > PPAPI: Fix WebSocket Var ref leak receiving binary > > BUG=173503 > > > Review URL: https://chromiumcodereview.appspot.com/12096099 This seems to have broken WebSocket tests on the mac bots http://build.chromium.org/p/chromium.mac/builders/Mac10.6%20Tests%20%281%29/builds/35419 http://build.chromium.org/p/chromium.mac/builders/Mac10.7%20Tests%20%281%29/builds/7829 TBR=dmichael@chromium.org Review URL: https://codereview.chromium.org/12096107 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180105 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Fix WebSocket Var ref leak receiving binarydmichael@chromium.org2013-02-011-3/+3
| | | | | | | | | BUG=173503 Review URL: https://chromiumcodereview.appspot.com/12096099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180093 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Get TrackedCallback ready for running on non-main threads.dmichael@chromium.org2012-11-051-4/+4
| | | | | | | | | | | | | | | | When CompletionCallbacks can run on background threads, ClearAndRun doesn't make sense anymore. Because the call may bounce to a different thread, we can't guarantee we'll run it right away, so setting the callback pointer to NULL is no longer a good way to indicate the callback has been run. Instead, callers should just use Run(), and rely on IsPending() to tell them if the call is still pending. TrackedCallback also can not use WeakPtrs, because those DCHECK if they are dereferenced on a different thread than they were created on. In particular, if a PPB implementation calls callback_->Run(PP_OK), that almost always happens on the main thread, and creates a WeakPtr<TrackedCallback> there. But Run will sometimes have to schedule a task on a non-main thread, and the WeakPtr will fail there. Note that because all this happens behind the proxy lock, it actually would be safe. But I just went with a bool flag to do the same checking as before, rather than try to subvert the WeakPtr checks. The CL for the Callbacks-on-background-threads feature is basically working and is here: https://chromiumcodereview.appspot.com/10910099 BUG=92909 Review URL: https://chromiumcodereview.appspot.com/10909244 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166009 0039d316-1c4b-4281-b951-d872f2087c98
* Provide IPC mechanism for host-to-resource messagingvictorhsieh@chromium.org2012-10-291-52/+26
| | | | | | | | | BUG= Review URL: https://chromiumcodereview.appspot.com/11267034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164577 0039d316-1c4b-4281-b951-d872f2087c98
* PluginResource: Avoid having two sets of similar methods for talking with ↵yzshen@chromium.org2012-10-161-6/+6
| | | | | | | | | | | | browser and renderer. BUG=None TEST=None Review URL: https://chromiumcodereview.appspot.com/11106019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162066 0039d316-1c4b-4281-b951-d872f2087c98
* Pepper WebSocket API: Implement new design Chrome IPC.toyoshim@chromium.org2012-10-091-0/+509
This change implements new Chrome IPC for PPB_WebSocket. After this change, all mode including out of process will work with new design. It doesn't depend on old SRPC design any more. BUG=87310,116317 Review URL: https://chromiumcodereview.appspot.com/10944005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160783 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-12 00:49:54 +0000