WebSocket: Use PassRefPtr<> in function arguments in WorkerThreadableWebSocketChannel.cpp
authoryutak@chromium.org <yutak@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 11 Aug 2011 14:00:57 +0000 (14:00 +0000)
committeryutak@chromium.org <yutak@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 11 Aug 2011 14:00:57 +0000 (14:00 +0000)
commit805a0701a69d9ad8869bbfacf6a7b58b3397498c
tree6bfe4c33e87885276b91f63f901f6f628fbcc50f
parent7c94c77f1a6091054f5cd0d567b6b041b0e748d8
WebSocket: Use PassRefPtr<> in function arguments in WorkerThreadableWebSocketChannel.cpp
https://bugs.webkit.org/show_bug.cgi?id=66047

Reviewed by Kent Tamura.

It's safe to use PassRefPtr<> in these functions because:
- CrossThreadTask knows how to pass a RefPtr<> across threads, and
- Call sites do not pass the pointers to anywhere else.

No change in functionality, thus no new tests.

* websockets/WorkerThreadableWebSocketChannel.cpp:
(WebCore::workerContextDidSend):
(WebCore::workerContextDidGetBufferedAmount):
(WebCore::workerContextDidConnect):
(WebCore::workerContextDidReceiveMessage):
(WebCore::workerContextDidStartClosingHandshake):
(WebCore::workerContextDidClose):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@92843 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/websockets/WorkerThreadableWebSocketChannel.cpp