Re: [asap] WS Message Delivery

["Mark Peel" <mpeel@novell.com>]

Keith and John,

  I saw a reference in another committee to WS-Addressing 2004 --
apparently an update of the WS-Addressing spec.  Do either of you know
anything about this?

Best wishes,

Mark Peel
Web Services Infrastructure
Novell, Inc.

>>> John Fuller <jfuller@wernervas.com> 5/20/2004 8:16:48 AM >>>
I agree.

I missed the Tuesday call because I was at an INFORMS conference, but 
while I was
there I proposed ASAP for optimization service instances, and there 
seemed to be some interest.

One thing some people brought up is that a lot of times you want to 
modify and
resolve a problem.  Right now the best I could offer was WS-CAF's
work,
but I argued that rather than stateful sessions, stateful service 
instances were
more scalable and addressable.

I think that if we could use wsdl to define operations for service 
instances,
that might help...

There was a discussion in WSDM last week about being able to generate
the complete WSDL component model from an endpoint reference,
perhaps by extending WS-Addressing to include a wsdl url
or just adopting a convention for urls so that a ?wsdl=... extension
returns the wsdl of interest.

At first glance, I thought WS-MessageDelivery might help with this
with the WSRef containing the relevant information.




On May 17, 2004, at 3:10 PM, Keith Swenson wrote:

> I finally had the chance to read WS Message Delivery. 
>
>  Unfortunately, it does not define any way to address a stateful web

> service, such as all the ASAP resources are.  It is strangely silent

> on this.  It does, however, define some thing that overlap with 
> WS-Reliability and it defines a callback message pattern which 
> operlaps with ASAP notifications.
>
> I believe we need a standard way to address resources as a stateful 
> web service.
>
> -Keith
>
> > -----Original Message-----
> > From: John Fuller [mailto:jfuller@wernervas.com] 
> > Sent: Tuesday, May 04, 2004 6:06 AM
> > To: ASAP
> > Subject: [asap] fyi
> >
> >
> > I mentioned the WS-MessageDelivery alternative to
> > WS-Addressing people 
> > are considering in WSRF.
> > Here's a presentation suggesting using WS References to identify
web 
> > services
> >
> > http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php 
> > /6586/WS-
> > Reference_and_Resource_ID.ppt
> >
> > and here's one for actually encoding property requests in the
>  > URL for 
> > an HTTP GET
> >
> > http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php 
> > /6589/WS-
> > Rest4WSRF.ppt
> >
> >
> > To unsubscribe from this mailing list (and be removed from
> > the roster of the OASIS TC), go to
> > http://www.oasis-open.org/apps/org/workgroup/asap/members/leav 
> > e_workgroup.php.
> >