Hi Sam,
That API proposal is not mandatory to be "the" WS-N API in Apache Hermes, i think it can be a higher level API.
This API tries to hide any Port definition(and WSRF) and tries to cover both WS-N and WS-Eventing.
Am i right, that you are expecting interface that work with "org.apache.wsrf.impl.notification" from the globus source?
As you can see in my proposal, some request must be modelled using WS-ResourceLifetime. Therefore an underlaying WS-N API is needed, which grants acces to the wsrf stuff.
So my proposal can be seen as an API ontop of a WS-N / WS-E API.
what you think about that?
stefan
Samuel Meder wrote:
On Fri, 2005-01-07 at 14:41 +0100, Stefan Lischke wrote:
Hi all,
i have discussed API things with Ian and after a first proposal, i'm doing a second, i dunno whats the attachment policy is for this list, so i put up the UML on:
http://www.ivs.tu-berlin.de/Lischke/blog/archives/2005/01/apache_hermes_a.html
hope to hear from you.
I would like to arrange a teleconference to talk about these APIs sometime next week (as they are significantly different from ours which we want to use to implement WS-N). Would Tuesday morning 9am central time work for everyone?
/Sam
btw. is there any chance i can participate in the wsn TC mailinglist from OASIS, without being an OASIS member?
thx stefan
-- My place : http://user.cs.tu-berlin.de/~lischke
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
