By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,934 Members | 1,449 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,934 IT Pros & Developers. It's quick & easy.

async service development

P: n/a
I am working on developing a series of web services around the jabber
protocol. I have written the necessary soap over jabber code on the
server side (java) and am now working on the client side in C#. I am
trying to determine a mode of development because the standard "create a
server side wsdl and generate client stubs" doesn't seem to work well.

I am new to async web services, so bear with me if I am doing this
wrong. What I envision happening is that I have a server side wsdl and
then a "client" wsdl (the client is being invoked from the server so
this seems more like two servers communicating). So for a stock
example, there would be a register(string stockname) on the server and
then the client would have receiveUpdate(StockPrice price) operation.

To use the register(stockname) method is simple enough, I just can just
write the service, use the Add Web Reference and write some glue code
between jabber and the service with WSE 2.0. But is it possible to
generate a stub for the client to get the receiveUpdate() message? I
looked at the wsdl.exe program and can only figure out how to generate a
client proxy, and not a stub where operations can be invoked (i.e. a
server stub)

So in summary, my question is, on the .NET side how do I enable it to
receive async events while still being able to use the WSDL generation
tools? Or more generally, what is the development pattern for these
types of services where the messages are flying each way?

Another scneario I thought of is that instead of a server and client
WSDL, there could just be a server wsdl, but that the receiveUpdate
operation would be defined something like:

<wsdl:operation name="receiveUpdate">
<wsdl:output message="tns:receiveUpdate" name="receiveUpdate"/>

But the tools kind of choke on that.


- Dan
Nov 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.