Smokey,
In this case, a channel sink is the only option you have. However, it
is a lot of work, quite frankly.
If you have an option, you can use WCF as well, and take a look at the
ClaimSet that the client requests. It's probably much easier to hook into
this.
If you do a google search on "remoting channel sink" you will probably
find a number of examples on how to create a remoting sink.
An easier way might be to place items into the current CallContext and
then retrieve them from the CallContext on the server side (this is
serialized and sent across the wire to the server).
If you are not using simple types, you will have to mark your type with
the ILogicalThreadAffinative interface so that it is serializes between the
app domains.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Smokey Grindel" <no****@nospam.comwrote in message
news:eH**************@TK2MSFTNGP03.phx.gbl...
>I don't want to use IIS, (design specifiaction) data security isnt an
issue, I just want to make a custom authorization and authentication system
for my remoting server... how would i do this? set up a custom channel sink
pair? any examples of something like this? I just need basic username and
password and the ability to know who sent what call to the server (username
only) thanks!
