Sunny
6/15/2004 8:03:00 PM
Then the short answer is to use some kind of ID in every method call.
Sunny
In article <eLz554wUEHA.2520@TK2MSFTNGP10.phx.gbl>,
kendrhyd@sympatico.ca says...
> I understand that "genuine channels" is a commercial product, which
> eliminates it from consideration since this project has no capital budget
> (only my time!).
>
> -ken
>
> "Sunny" <sunnyask@icebergwireless.com> wrote in message
> news:%23ult6vwUEHA.220@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > with build-in channels, you have to implement it by yourself, either by
> > passing some ID in every method call, or by creating some custom channel
> > sync, in which you add this ID.
> >
> > You may try genuine channels, as they have methods for identifying every
> > connection among all other good things.
> >
> > Sunny
> >
> > In article <Or81mkvUEHA.2484@TK2MSFTNGP11.phx.gbl>,
> > kendrhyd@sympatico.ca says...
> > > Aside from adding a parameter to every remoted procedure call, is there
> any
> > > way for a remoted server object, especially a singleton that can accept
> > > connections from multiple concurrent clients, to determine which client
> > > issued the method invocation?
> > >
> > > I want to create multiple clients that can connect to the same remoted
> class
> > > instance, and permit changes made to the server object to be broadcast
> to
> > > all connected clients -- but I want each client to be able to determine
> > > whether the broadcast originated from that client or another client.
> > >
> > > -ken
> > >
> > >
> > >
>
>
>