Davanum Srinivas wrote:
Yes Alek. Am trying to set that up.
let make sure that there are multiple people having admin access to be
able to monitor and restart this service if needed - i volunteer to help
with that.
thanks,
alek
On 5/30/05, Aleksander Slominski <[EMAIL PROTECTED]> wrote:
Jaliya Ekanayake wrote:
Hi All,
We would like to propose a release for Apache Sandesha
WS-ReliableMessaging implementation.
Motivation:
It has been quite some time since we have updated Sandesha to reflect
the latest changes in the WS-ReliableMessaging specification (February
2005). Last few weeks we have tested Apache Sandesha with other
similar implementations, like IBM, Microsoft and Systinet. We were
able to pass all the available interop tests with the above
implementations. Now (After applying the changes that we identified
during the interop tests) we would like to propose a release for Sandesha.
Features:
Following features are available in the release of Sandesha,
(1) Implementation of WS-ReliableMessaging specification (February
2005). On top of Axis 1.x
(2) INORDER delivery assurance.
(3) Support for synchronous and asynchronous reliable exchange of
messages.
(4) A Client API that will make it easy for users to work
simultaneously with different endpoints and different message sequences.
(5) Updated documentation.
(6) Support for WS-Policy integration.
Since Axis 1.2 was released recently, we believe that it is a good
time for a stable version of Sandesha as well.
Release Plan:
We would like to release a beta version as soon as possible.
If there are no complaints, we would like to release Sandesha-1.0
within a week after the beta release.
I'm +1 for doing the release with the above features.
+1 and i would add that there should be a permanent interop service
running on one of apache servers with the latest version of sandesha.
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay
--
The best way to predict the future is to invent it - Alan Kay
