Question on using System.Runtime.Remoting.Messaging.header_members to find a well-known object in a sniffed port
- From: "DotNetterInternals" <dotnetterinternals@xxxxxxxxxxx>
- Date: 15 Jul 2006 13:03:38 -0700
Hello:
Suppose that I have a port sniffer/analizer and also the entire source
code to a (managed) .NET remoting app. The sniffer certainly makes it
easy to log and to display the port's traffic that I send with a .NET
remoting call.
Further suppose that the sniffer listens on a well known port and then
logs the binary (not SOAP) format of a .NET serialized remoting call.
(Dont worry, this is all legal. :) I'm thinking of using this
technique to develop a highly customized in-house .NET debugging
utility for deserializing and deciphering the bits from the sniffer's
binary log).
Question:
Is there enough information in the Microsoft 'remoting header'
http://msdn2.microsoft.com/en-us/library/system.runtime.remoting.messaging.header_members.aspx
to:
1. Allow me to identify the well-known object in the log
[Header.ToString() method looks promising]
2. Deserialize, then populate that well-known object from log data.
3. Last, examine with the debugger, to examine that newly populated
object.
I am not expecting to populate deep objects. Just a shallow object
would suffice for now.
TIA
dotnetterinternals@xxxxxxxxxxx
.
- Prev by Date: Re: Throwing exceptions in custom server sink
- Next by Date: Re: URGENT PLZ........File Upload in .NET Remoting
- Previous by thread: Re: URGENT PLZ........File Upload in .NET Remoting
- Next by thread: Cross-AppDomain remoting strangeness
- Index(es):