.NET & Java Publish-Subscribe pattern
- From: Ludwig Wittgenstein <sender_001@xxxxxxxxxxx>
- Date: Tue, 05 Jun 2007 00:08:26 -0000
Hello, all.
Does anyone know of documentation about implementing a publish-
subscribe model between a .NET Web service provide and a Java service
consumer? I have this problem I am trying to solve, and would greatly
appreciate it if someone can tell me what the best solution would be
for it.
I have a .NET 2.0 (ASMX) webservice on a server on a dedicated hosting
server, and several clients in different cities running linux servers
with MySQL, usually their MySQL server is synchronized with one I have
on a dedicated hosting server. This is easy to do, I just have web
service clients on each linux server calling webmethods on the .NET2.0/
SQL server and push information whenever there is a change in the
database. The problem is that I want to put data on the .NET2.0/SQL
server and have it propagated on all the MySQL servers. What is the
best way to do this? I believe a naive (?) solution would be to have
web service clients on the linux machines polling the .NET2.0 web
service every once in a while asking for data. However, I think that a
publish-subscribe model best fits this scenario, so that I can have
the .NET2.0 server publish new updates, send events to the subscribes
(the linux servers endpoint), which in turn will update the data on
their MySQL servers. What's the possible way to implement that? I'm
not asking someone to design it for me, I just want to be pointed into
the right technology-direction, I have the following solutions in
mind, let me know if I'm right or not:
1. use WS-Eventing: the .NET2.0 server publishes, and Apache Axis
webservices on each Linux client will subscribe to it.
2. Have JMS clients the Linux machines subscribe to a channel created
somehow by the .NET2.0 endpoint (is that possible?). The .NET2.0
service will send messages to all subscribers.
Thanks a lot,
.
- Follow-Ups:
- Re: .NET & Java Publish-Subscribe pattern
- From: PlatinumBay
- Re: .NET & Java Publish-Subscribe pattern
- Prev by Date: Encrypting SOAP Envelope
- Next by Date: UPDATE: Adding/Updating Web Reference takes ~ 2 minutes
- Previous by thread: Encrypting SOAP Envelope
- Next by thread: Re: .NET & Java Publish-Subscribe pattern
- Index(es):
Relevant Pages
|