axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject RE: Suggestions on next release
Date Mon, 26 Apr 2004 06:31:06 GMT
Please consider thread safty as well to enable running multiple clients simultaneously.

Thnaks,
Samisa...


--- Susantha Kumara <susantha@opensource.lk> wrote:
> Hi Samisa
> 
> My personal idea is not trying to improve the existing AxisTransport
> because its missing following
> 
> 1. Chuncked data support
> 2. Understanding http protocol that we need according to WS-I
> specifications. ie
> 	HTTP Authentication
> 	Expect-extensions
> 	Content-Encoding
> 	Trasfer-Encoding
> 	Upgrade header
> 	Other required headers (session support etc)
> 3. No proper error handling
> 
> One other thing is that this transport layer allocates/deallocates
> memory for its buffers for each and every request. But according to the
> Axis C++ architecture (pull parsing and non blocking serialization) each
> thread can have its own fixed size buffer in the transport layer as long
> as thread exists. This way we can improve performance.
> 
> We can have a buffer pool too :) :)
> 
> So its a good idea to write a new transport layer with the help of
> existing transport layer code.
> 
> ---
> Susantha.
> 
> ---
> But admire a different tree each day
> ---
> 
> On Fri, 2004-04-23 at 01:46, Samisa Abeysinghe wrote:
> > Hi Susantha,
> >     Is there any way of making the transport layer thrad safe?
> >    
> >     (In other words; why the transport layer cannot be made thread
> > safe?)
> >  
> >     In a real world deployment we expect the axis client to be thread
> > safe.
> > Thanks,
> > Samisa...
> > 
> > Susantha Kumara <susantha@opensource.lk> wrote:
> >         As far as I know only the AxisTransport code is not thread
> >         safe. We are going to improve the the transport API to
> >         support,
> >         
> >          
> >         
> >         1. Implementing other transport layers than http
> >         
> >         2. Setting and getting key value pairs other than Axis
> >         predefined headers such as SOAPAction header
> >         
> >          
> >         
> >         Then we are going to make the transport to be a separate
> >         library that is dynamically loaded (explicitly with dlopen
> >         etc). Then its a requirement that any transport library (.dll
> >         or .so) should be thread safe by it self.
> >         
> >          
> >         
> >         When we separate the transport code as described above I can
> >         assure that rest of the code is thread safe.
> >         
> >          
> >         
> >         Thanks,
> >         
> >          
> >         
> >         Susantha
> >         
> >          
> >         
> >         -----Original Message-----
> >         
> >         From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com] 
> >         
> >         Sent: Tuesday, April 20, 2004 4:55 PM
> >         
> >         To: Apache AXIS C Developers List
> >         
> >         Subject: Re: Suggestions on next release
> >         
> >          
> >         
> >         Hi All,
> >         
> >             What about thread safty?
> >         
> >         Thanks,
> >         
> >         Samisa...
> >         
> >          
> >         
> >         --- damitha@opensource.lk wrote:
> >         
> >         > Hi all,
> >         
> >         >     I make a suggestion that Axis C++ should release
> >         frequently with 
> >         
> >         > less durations between the releases. I think release 1.1
> >         gave a good 
> >         
> >         > example of this. So I suggest that we go for a 1.2
> >         immediately. For 
> >         
> >         > that I have few suggestions.
> >         
> >         > 
> >         
> >         > Fix the bugs associated with release 1.1 and incorporate
> >         them into 1.2 
> >         
> >         > appropriately.(and/or make a hot fix release for 1.1)
> >         
> >         > 
> >         
> >         > Create an automated testing mechanism that makes the life
> >         easier for 
> >         
> >         > project that make frequent releases.
> >         
> >         > 
> >         
> >         > Start discussions on what features that should be added to
> >         1.2
> >         
> >         > 
> >         
> >         > 
> >         
> >         > damitha.
> >         
> >          
> >         
> >          
> >         
> >          
> >         
> >               
> >         
> >                     
> >         
> >         __________________________________
> >         
> >         Do you Yahoo!?
> >         
> >         Yahoo! Photos: High-quality 4x6 digital prints for 25
> >         http://photos.yahoo.com/ph/print_splash
> >         
> >          
> >         
> >          
> >         
> >          
> >         
> >         
> > 
> > ______________________________________________________________________
> > Do you Yahoo!?
> > Yahoo! Photos: High-quality 4x6 digital prints for 25
> 



	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25
http://photos.yahoo.com/ph/print_splash

Mime
View raw message