Hi Sam,
Samuel Meder wrote:
On Fri, 2005-01-07 at 17:53 +0100, Stefan Lischke wrote:I had this thought first too, pls look at the first UML diagram i did at:
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.
I think that your API description as is does not provide me with enough detail to really determine whether that is a achievable goal.
One immediate comment while we are at it is that subscribe in both WS-E
and WS-N is in some sense a factory operation and should definitely not
be modeled in the same interface as operations on the entity a subscribe
creates.
http://crewman-3.ivs.tu-berlin.de/SubscriberSeq.gif
But Ian, convinced me, that its nicer to merge SubscriptionManager and Subscriber (in the above diagram), so we have an Interface that can be implemented on every side (subscriber, publisher).
But lets wait till he said something.
I'm @ICQ(14558246) and on #apache-ws-fx @irc.freenode.org (nick lischke),
If you use miranda, just get the irc plugin and we can chat. Thats also the way i communicate with Ian.
(I'm away eating supper back in 1 h)
stefan
-- My place : http://user.cs.tu-berlin.de/~lischke
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
