Hi, Hm.. interesting scenario..Please see my comments below.
Thanks, Jaliya ----- Original Message ----- From: IVO To: Benjamin Schmeling ; [email protected] Sent: Tuesday, November 29, 2005 2:50 PM Subject: Re: Oneway ws and reliability Hi, i have a project that requires the use of either a message broker or web services. HINT: Intend to transfer all daily sales of burger king stores to headquarter. this implies an average of 2000 stores connect to headquarter with 2hours window of transaction. also the possibility of burger-king headquarter to broadcast price changes to all stores. With message brokers this is possible like JMS or propriatory ones using publishing and subscription. Have made studies on WS-RM, WS-Security, WS-Conversation, WS-Callback, and WS-Policy and thought web services with their interop.. they are better than JMS and other MOM. I have had a look on Sandesha as regards to WS-RM. It was quite interesting. My qeuestions after reading this mail of using sequences in talking to three WS: 1. Having the same messages for web service A, B, and C is there a means to braodcast the messages without any interation in application level but by sim ply listing the endpoints? Sandesha does not have a message broadcasting machanism at the transport level and it is not a requirement of the WS-RM specs. For this functionality you have to use some mediation service. Apache Synapse will do this soon :) 2. Has Sandesha some implementations of load balance? BEA uses Buffers. Say 2000 stores all talk simultaneously to one WS. Sandesha does not have a built in load balancing mechanism. But it may be able to handle the load as long as Servlet container and Axis is handling the load. 3. Has Sandesha in built tools for monitoring the flow of information at transport level or do i have define my handlers for that? You can add handler to both request and response flows to monitor the message flow. 4. What about WS-Conversation and Callback? Implementation of WS-SecCon is still not complete thanks Benjamin Schmeling <[EMAIL PROTECTED]> wrote: Hi, imagine the scenario, described in the reliable messaging specification. Now lets assume the webservices are all oneway and the second message goes to a third endpoint. I know the specification supports only two endpoints, but is there a possibility to do the following: 1.) call webservice A (at http:/abc.org) 2.) call webservice B (at http:/cde.org) 3.) call webservice C (at http:/abc.org) I could do this with 3 separate sequences. At every end of one sequence endSequence() is called in Sandesha. Can I make the conclusion that after calling endSequence() the message to all webservices in the sequence are already successfully delivered? For example: new SandeshaContext() call webservice A (at http:/abc.org) endSequence() // /message to A has been delivered already at this point of code?/ new SandeshaContext() call webservice B (at http:/cde.org) .... ... .. Thanks, Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------------------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
