Hello Dominick, thank you so much for your response.
Questions tho:
" you either use the duplex support in WCF to store the CallbackChannels
internally and call back through them whenever an event occurs."
If we have a callback that users subscribe to, how do we alert only a
particular client named 'flappy' that has subscribed to the callback?
"Or have your own infrastructure where the client news up a ServiceHost and
you pass a callback URI to the service for later notification."
Im still missing the part of how to raise the event for only a specific user
- or am i thinking too hard? ie:
For instance if 3 users subscribed to the event SomethingHappened();
How can i say raise the event SomethingHappened() only for user number 2?
For some reason im having a hard time grasping how this would actually work.
Thanks again for your comments, i hope to hear more :-)
> Hi,
>
[quoted text clipped - 34 lines]
> >
> > Thanks in advance :-)
Dominick Baier - 27 Nov 2007 19:30 GMT
how about storing the callback reference in a dictionary<string, channel>
that maps the user to a callback channel?
-----
Dominick Baier (http://www.leastprivilege.com)
Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp)
> Hello Dominick, thank you so much for your response.
>
[quoted text clipped - 62 lines]
>>>
>>> Thanks in advance :-)
aiKeith - 27 Nov 2007 20:25 GMT
OK, this may be the part i was missing. So each CallBackChannel is specific
to only one user?
:-)
> how about storing the callback reference in a dictionary<string, channel>
> that maps the user to a callback channel?
[quoted text clipped - 70 lines]
> >>>
> >>> Thanks in advance :-)
Dominick Baier - 27 Nov 2007 20:41 GMT
yep ;)
-----
Dominick Baier (http://www.leastprivilege.com)
Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp)
> OK, this may be the part i was missing. So each CallBackChannel is
> specific to only one user?
[quoted text clipped - 75 lines]
>>>>>
>>>>> Thanks in advance :-)
aiKeith - 27 Nov 2007 22:56 GMT
Thanks for sticking with me. It all makes sense now, especially after
creating a complete working version - the piece i was completely missing was:
<ServiceBehavior(InstanceContextMode:=InstanceContextMode.PerSession,
ConcurrencyMode:=ConcurrencyMode.Multiple)> _
The PerSession makes sense, i was assuming it was always a singleton, thus
all clients were using the same 'instance' of the object - obv. not so with
PerSession.
Thanks again for your help. Have a great one !!!
> yep ;)
> -----
[quoted text clipped - 81 lines]
> >>>>>
> >>>>> Thanks in advance :-)