> There is a WS-Eventing specification for web services enhancements that
> might do the trick. Have a look at
> http://blogs.msdn.com/bwill/archive/2004/02/10/70964.aspx which also has a
> link to the microsoft spec.
>
> Alternatively, you could roll your own. Have a web service that accepts
> subscribers and writes their "response" web service URL into a database.
> When you need to fire an event, all the stored subscribers are sent a
> particular web service message to the URL they have sent you and is in
your
> database.
>
> Note:: I have not yet tried WS-Eventing, but it is (yet another) standard
in
> the WS-* family and is a more interoperable way to go.
>
> --
> - Paul Glavich
> Microsoft MVP - ASP.NET
>
>
> "Ice" <ice@nospam.com> wrote in message
> news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> > All -
> >
> > I'm curious to know how others are handling events that need responded
to
> > across machine boundaries. In my situation would like the events to
> happen
> > asynchronously also.
> >
> > I've seen that using Remoting + events is not the most stable solutions.
> > I've also heard about using LCE or UDP for multicast.
> >
> > I was hoping people have experiences which they could share with me.
> >
> > Thanks.
> > ice
> >
> >
>
>

"Ice" <ice@nospam.com> wrote in message
news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> All -
>
> I'm curious to know how others are handling events that need responded to
> across machine boundaries. In my situation would like the events to
happen
> asynchronously also.
>
> I've seen that using Remoting + events is not the most stable solutions.
> I've also heard about using LCE or UDP for multicast.
>
> I was hoping people have experiences which they could share with me.
>
> Thanks.
> ice
>
>

"Angelos Karantzalis" <akarantzalis@agiltech.gr> wrote in message
news:#HMbh9bvEHA.1400@TK2MSFTNGP11.phx.gbl...
> Have you thought of MSMQ, or is there some reason you can't use that ?
>
> You could use .NET Remoting & some sort of event manager on a "central"
> server that notifies using "Callback" objects on each client - I've seen a
> relative article on MSDN that talked about notifications of concurrent
> updates on data using VB.NET & remoting, however I can't really remember
> where on MSDN I saw it .. but it was exactly the solution you're looking
> for.
>
> Angel
> O:]
>
>
> "Ice" <ice@nospam.com> wrote in message
> news:uMOWwCCvEHA.4020@TK2MSFTNGP10.phx.gbl...
> > thanks for your reply Paul. At the moment, I'm not really concerned
with
> > interoperability - I'm just looking for something to implement pub/sub
> > patterns.
> >
> > Have you used LCE?
> > ice
> > "Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in
> > message news:es9GRjBvEHA.944@TK2MSFTNGP11.phx.gbl...
> > > There is a WS-Eventing specification for web services enhancements
that
> > > might do the trick. Have a look at
> > > http://blogs.msdn.com/bwill/archive/2004/02/10/70964.aspx which also
has
> a
> > > link to the microsoft spec.
> > >
> > > Alternatively, you could roll your own. Have a web service that
accepts
> > > subscribers and writes their "response" web service URL into a
database.
> > > When you need to fire an event, all the stored subscribers are sent a
> > > particular web service message to the URL they have sent you and is in
> > your
> > > database.
> > >
> > > Note:: I have not yet tried WS-Eventing, but it is (yet another)
> standard
> > in
> > > the WS-* family and is a more interoperable way to go.
> > >
> > > --
> > > - Paul Glavich
> > > Microsoft MVP - ASP.NET
> > >
> > >
> > > "Ice" <ice@nospam.com> wrote in message
> > > news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> > > > All -
> > > >
> > > > I'm curious to know how others are handling events that need
responded
> > to
> > > > across machine boundaries. In my situation would like the events to
> > > happen
> > > > asynchronously also.
> > > >
> > > > I've seen that using Remoting + events is not the most stable
> solutions.
> > > > I've also heard about using LCE or UDP for multicast.
> > > >
> > > > I was hoping people have experiences which they could share with me.
> > > >
> > > > Thanks.
> > > > ice
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"Ice" <ice@nospam.com> wrote in message
news:uMOWwCCvEHA.4020@TK2MSFTNGP10.phx.gbl...
> thanks for your reply Paul. At the moment, I'm not really concerned with
> interoperability - I'm just looking for something to implement pub/sub
> patterns.
>
> Have you used LCE?
> ice
> "Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in
> message news:es9GRjBvEHA.944@TK2MSFTNGP11.phx.gbl...
> > There is a WS-Eventing specification for web services enhancements that
> > might do the trick. Have a look at
> > http://blogs.msdn.com/bwill/archive/2004/02/10/70964.aspx which also has
a
> > link to the microsoft spec.
> >
> > Alternatively, you could roll your own. Have a web service that accepts
> > subscribers and writes their "response" web service URL into a database.
> > When you need to fire an event, all the stored subscribers are sent a
> > particular web service message to the URL they have sent you and is in
> your
> > database.
> >
> > Note:: I have not yet tried WS-Eventing, but it is (yet another)
standard
> in
> > the WS-* family and is a more interoperable way to go.
> >
> > --
> > - Paul Glavich
> > Microsoft MVP - ASP.NET
> >
> >
> > "Ice" <ice@nospam.com> wrote in message
> > news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> > > All -
> > >
> > > I'm curious to know how others are handling events that need responded
> to
> > > across machine boundaries. In my situation would like the events to
> > happen
> > > asynchronously also.
> > >
> > > I've seen that using Remoting + events is not the most stable
solutions.
> > > I've also heard about using LCE or UDP for multicast.
> > >
> > > I was hoping people have experiences which they could share with me.
> > >
> > > Thanks.
> > > ice
> > >
> > >
> >
> >
>
>

"Ice" <ice@nospam.com> wrote in message
news:uMOWwCCvEHA.4020@TK2MSFTNGP10.phx.gbl...
> thanks for your reply Paul. At the moment, I'm not really concerned with
> interoperability - I'm just looking for something to implement pub/sub
> patterns.
>
> Have you used LCE?
> ice
> "Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in
> message news:es9GRjBvEHA.944@TK2MSFTNGP11.phx.gbl...
> > There is a WS-Eventing specification for web services enhancements that
> > might do the trick. Have a look at
> > http://blogs.msdn.com/bwill/archive/2004/02/10/70964.aspx which also has
a
> > link to the microsoft spec.
> >
> > Alternatively, you could roll your own. Have a web service that accepts
> > subscribers and writes their "response" web service URL into a database.
> > When you need to fire an event, all the stored subscribers are sent a
> > particular web service message to the URL they have sent you and is in
> your
> > database.
> >
> > Note:: I have not yet tried WS-Eventing, but it is (yet another)
standard
> in
> > the WS-* family and is a more interoperable way to go.
> >
> > --
> > - Paul Glavich
> > Microsoft MVP - ASP.NET
> >
> >
> > "Ice" <ice@nospam.com> wrote in message
> > news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> > > All -
> > >
> > > I'm curious to know how others are handling events that need responded
> to
> > > across machine boundaries. In my situation would like the events to
> > happen
> > > asynchronously also.
> > >
> > > I've seen that using Remoting + events is not the most stable
solutions.
> > > I've also heard about using LCE or UDP for multicast.
> > >
> > > I was hoping people have experiences which they could share with me.
> > >
> > > Thanks.
> > > ice
> > >
> > >
> >
> >
>
>

> I haven't used LCE before.
>
> The pub/sub pattern is relatively easy to implement and the WS-Evemting
spec
> is just a formalisation of that. Just provide a subscription web service
> that will take a 'notification' URl as its parameter. Send out messages to
> the URL specified when required. I know its an oversimplification, but I
am
> not aware of any all ready rolled implementations that will suit you.
>
> --
> - Paul Glavich
> Microsoft MVP - ASP.NET
>
>
> "Ice" <ice@nospam.com> wrote in message
> news:uMOWwCCvEHA.4020@TK2MSFTNGP10.phx.gbl...
> > thanks for your reply Paul. At the moment, I'm not really concerned
with
> > interoperability - I'm just looking for something to implement pub/sub
> > patterns.
> >
> > Have you used LCE?
> > ice
> > "Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in
> > message news:es9GRjBvEHA.944@TK2MSFTNGP11.phx.gbl...
> > > There is a WS-Eventing specification for web services enhancements
that
> > > might do the trick. Have a look at
> > > http://blogs.msdn.com/bwill/archive/2004/02/10/70964.aspx which also
has
> a
> > > link to the microsoft spec.
> > >
> > > Alternatively, you could roll your own. Have a web service that
accepts
> > > subscribers and writes their "response" web service URL into a
database.
> > > When you need to fire an event, all the stored subscribers are sent a
> > > particular web service message to the URL they have sent you and is in
> > your
> > > database.
> > >
> > > Note:: I have not yet tried WS-Eventing, but it is (yet another)
> standard
> > in
> > > the WS-* family and is a more interoperable way to go.
> > >
> > > --
> > > - Paul Glavich
> > > Microsoft MVP - ASP.NET
> > >
> > >
> > > "Ice" <ice@nospam.com> wrote in message
> > > news:uJt6Ss3uEHA.3728@TK2MSFTNGP12.phx.gbl...
> > > > All -
> > > >
> > > > I'm curious to know how others are handling events that need
responded
> > to
> > > > across machine boundaries. In my situation would like the events to
> > > happen
> > > > asynchronously also.
> > > >
> > > > I've seen that using Remoting + events is not the most stable
> solutions.
> > > > I've also heard about using LCE or UDP for multicast.
> > > >
> > > > I was hoping people have experiences which they could share with me.
> > > >
> > > > Thanks.
> > > > ice
> > > >
> > > >
> > >
> > >
> >
> >
>
>