Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of MEVENO@generali.fr designates
 193.57.141.200 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Asynchronous Invocation and connection keep alive on the TCP
 level
Date: Thu, 6 Aug 2009 16:39:21 +0200
Message-ID: <DB994DA6511E3246AE46C893817E326004232E96@EVS1.Groupe.Generali.fr>
In-Reply-To: <cfdb37fb0908060703u4c091abeo82e5077b78144425@mail.gmail.com>
Thread-Topic: Asynchronous Invocation and connection keep alive on the TCP
 level
Thread-Index: AcoWntQiYYZFDM5eRde+PcnlFdP2VgABKuhQ
References: <24835434.post@talk.nabble.com>
 <e507996c0908060254r7a395143h76eeae3e0b0df4bd@mail.gmail.com>
 <cfdb37fb0908060703u4c091abeo82e5077b78144425@mail.gmail.com>
From: "EVENO Manuel" <MEVENO@generali.fr>
To: <users@cxf.apache.org>


Do you have example or documentation of a "decoupled response endpoint"
or the callbacks-tyle mecanism you wrote about ?
I can find anything on the CXF Wiki ...

Manuel

-----Message d'origine-----
De : Eoghan Glynn [mailto:eoglynn@gmail.com]=20
Envoy=E9 : jeudi 6 ao=FBt 2009 16:04
=C0 : users@cxf.apache.org
Objet : Re: Asynchronous Invocation and connection keep alive on the TCP =
level

Andrew is correct.

JAX-WS async is purely a convenience mechanism to allow the application =
avoid creating a separate thread to manage the invocation direction.

What you really need to avoid is tying up the client->server connection =
for the duration of the long-running invocation.

This could be achieved via WS-Addressing with a decoupled response =
endpoint , so that the client->server may be torn down once the request =
has been transmitted and the response when ready is sent over a separate
server->client connection. Though it sounds like WS-A is not an option=20
server->for
you.

Otherwise you can model a polling-style (as suggested by Glen) or =
callback-style of interaction in the WSDL.

Cheers,
Eoghan


2009/8/6 Andrew Clegg <andrew@nervechannel.com>

> 2009/8/5 conficio <KajKandler@conficio.com>:
>
> > My question is: Does the asynchronous Web service some active=20
> > polling
> across
> > the TCP connection to keep it alive? Is that the solution I'm=20
> > looking
> for,
> > Asynchronous invocation?
>
> I'm happy to be corrected if wrong, but I believe the actual TCP=20
> conversation is basically the same for CXF sync/async service=20
> invocation, it just *appears* to work asynchronously from the POV of=20
> the client code.
>
> For really long-running jobs you are probably better off doing proper=20
> server-side asynchronous services with persistent state, like this:
>
> http://www.jroller.com/gmazza/entry/creating_service_side_asynchronous
> _web
>
> Andrew.
>
> --
> :: http://biotext.org.uk/ ::
>