Fix issue of localDescription and remoteDescription getter.

Source/modules/mediastream/RTCVoidRequestImpl.cpp

Index: Source/modules/mediastream/RTCVoidRequestImpl.cpp
diff --git a/Source/modules/mediastream/RTCVoidRequestImpl.cpp b/Source/modules/mediastream/RTCVoidRequestImpl.cpp
index cfde690ae9e9f1c023e2531a64e4084fc4396ebd..0dbcb32b010997a72f306e83887ddf3d91f6a7ab 100644
--- a/Source/modules/mediastream/RTCVoidRequestImpl.cpp
+++ b/Source/modules/mediastream/RTCVoidRequestImpl.cpp
@@ -60,6 +60,8 @@ RTCVoidRequestImpl::~RTCVoidRequestImpl()
 void RTCVoidRequestImpl::requestSucceeded()
 {
     bool shouldFireCallback = m_requester ? m_requester->shouldFireDefaultCallbacks() : false;
+    m_requester->updateLocalSessionDescriptionIfNeeded(true);

[Jens Widell, 2015/05/05 06:31:20]

To be completely correct, I think you should keep track of whether the request
is about updating the local or remote description (or neither) and only update
the right one.

[changbin, 2015/05/05 07:02:29]

I see. Then how about add argument |request_type| for RTCVoidRequestImpl
creator, and update local or remote description, or nothing per |request_type|
value? 

[Jens Widell, 2015/05/05 07:17:22]

Something like that, yes. But then it might actually make more sense to simply
have "m_requester->requestSucceeded(request_type)" here, and thus let
RTCPeerConnection decide what to do about it.

[changbin, 2015/05/05 07:32:19]

Yeah, that could be another option. But I'm afraid it brings more efforts than
the first option. There might be two concerns,
1. Do we actually want to introduce |request_type| for the interface
|RTCVoidRequest|?
2. Need to add change in Chromium implementation to send request_Type in
'm_requester->requestSucceeded(request_type)'.
https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/m...

+    m_requester->updateRemoteSessionDescriptionIfNeeded(true);
     if (shouldFireCallback && m_successCallback)
         m_successCallback->handleEvent();