You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Helen Pugmire <pu...@bellatlantic.net> on 2000/12/13 14:51:20 UTC

unsubscribe soap-dev

unsubscribe soap-dev

Glen Daniels wrote:

> Comments inline:
>
> ----- Original Message -----
> From: "Steve Graham" <sg...@us.ibm.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, December 12, 2000 8:52 AM
> Subject: Re: Requirements - 2000/12/11
>
> > I think it is quite useful to have the possibility of an AXIS engine
> > supporting start/stop/update of services.
> > I am not sure it is a requirement of the engine, however.  I believe that
> > the start/stop functionality can be handled as a handler, or a subclass of
> > a router.
>
> Certainly could work this way, but I would remind you of the caution against
> "microkernel-izing".  Not everything necessarily needs to be, or is best
> designed as, a handler... :)
>
> > As far as update of services is concerned, perhaps we should state this as
> > a requirement, clearly state that deployment of an "update" to an existing
> > web service should affect subsequent invocations of that web service, but
> > not impact any current invocation.
>
> +1