[Mono-dev] Remoting HTTPServerChannel does not populate channel uri in all cases
Roei Erez
roeie at mainsoft.com
Tue Feb 12 05:00:12 EST 2008
Hi,
I have noticed that when registering an HttServerChannel in Remoting,
the channel's uri's are not always populated.
This causes a problem when the server is asked to serialize an 'ObjeRef'
for a client activated object as response, since its inner Channelnfo
does not contain the appropriate uri's.
This will obviously cause the client to fail interact using this ObjRef.
Attached is a patch that solves this problem as it is done in
TcpServerTransportSink.cs.
Please approve and I will commit.
Regards,
Roei Erez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080212/f0d8b43b/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RemotingCAO.patch
Type: application/octet-stream
Size: 732 bytes
Desc: RemotingCAO.patch
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080212/f0d8b43b/attachment-0001.obj
More information about the Mono-devel-list
mailing list