- 02 Apr, 2008 23 commits
-
-
Alexander Morozov authored
-
Nikolay Sivov authored
-
Mikołaj Zalewski authored
-
James Hawkins authored
-
James Hawkins authored
-
EA Durbin authored
-
Hwang YunSong(황윤성) authored
-
Alexandre Julliard authored
-
Rob Shearman authored
-
Rob Shearman authored
Use FormatMessage to get the message for the Win32 error.
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
Don't hold locks while forwarding messages, instead rely on the reference count. This prevents some really fun deadlocks from occuring.
-
Maarten Lankhorst authored
-
Vitaliy Margolen authored
-
Vitaliy Margolen authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
- 01 Apr, 2008 17 commits
-
-
Apostolos Alexiadis authored
-
Apostolos Alexiadis authored
-
Apostolos Alexiadis authored
-
Aric Stewart authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
-
Maarten Lankhorst authored
Just to be cautious, since it reads 4 bytes it should stop trying at EOF-3. Also be more strict with the return values.
-
Maarten Lankhorst authored
-
Alexandre Julliard authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Rob Shearman authored
-
Rob Shearman authored
-
Rob Shearman authored
rpcrt4: Add a reference to the binding object in I_RpcNegotiateTransferSyntax and release the reference in I_RpcFreeBuffer. This is needed because a context binding handle could be released on unmarshall, but it still needs to stay valid until the binding handle is no longer being used. Re-use the previously unused RPCRT4_ExportBinding function as RPCRT4_AddRefBinding and rename RPCRT4_DestroyBinding to RPCRT4_ReleaseBinding to show that it's purpose is to release a reference count and destroy if necessary, not always destroy.
-