On Tue, 2008-01-29 at 13:59 -0800, Mike McKee wrote: > We are using Simple Server. I am only interested in the Server Side. > >From the looks of the code, it looks like AXIS2C Closes the connection > after each request. This causes problems for Clients (Microsoft and > others) who explicitly put things like Keepalive, or Continue in the > headers. Our interest is in using simple server, as a server that we are > going to imbed in our application. > > Is this recommended usage of AXIS2C, or do most people imbed in IIS or > APACHE?
For a production environment we recommend using Axis2/c with Apache. Because Apache can handle concurrent requests without much degradation in performance. -Manjula, > > > > -----Original Message----- > From: Dinesh Premalal [mailto:[EMAIL PROTECTED] On Behalf Of Dinesh > Premalal > Sent: Monday, January 28, 2008 9:15 PM > To: axis-c-dev@ws.apache.org > Subject: Re: Can AXIS2C do this? > > Hi Mike, > > "Mike McKee" <[EMAIL PROTECTED]> writes: > > 2. I noticed that CONNECTION- KEEPALIVE is giving us trouble when we > use AXIS2C > > Server with HTTP 1.1 (Microsoft Developer Studio Web Services Client). > In > > looking at the AXIS2C source code, it appears that socket connections > are > > always being closed, and that KEEPALIVE is not supported. Can you > > confirm. > > In order to support KEEPALIVE you need to have your services on > Apache2 (mod_axis2) and on client side need to build Axis2/C with > libcurl enabled. > > ./configure --enable-libcurl=yes [other options] > > thanks, > Dinesh > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
