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: Do we need to keep LibWWW transport updated
Date Mon, 22 Nov 2004 06:42:36 GMT
Thoughts on LibWWW transport came too late I guess. I have already removed it last week :(
Samisa...

--- sanjaya singharage <sanjayas@opensource.lk> wrote:

> After thinking about this for some time, I also think I have to agree with
> damitha. If someone does decide to maintain an unmaintained module it would
> require some effort to get things going again. This could casue hindrance to
> a volunteer willing to take up maintainance of a certain module that was
> removed thereby discouraging them. Now I think the even the removal from
> build systems should be done in such a way so that they can be re-added
> easily later. e.g. Simply reomve a project from the vc workspace and let the
> relevant project files stay where they are. If needed to reawaken the
> project simple add it back to the workspace. For make and ant...?
> 
> So I suggest to keep a file say modules.txt at ws-axis/c.
> 
> Here is something to start with. please correct any item as necessary
> 
> Module                                    Role
> Status
> 
> Apache 1.3.X module          Server Transport plugin            maintained
> Apache 2.X module             Server Transport plugin            maintained
> Axis2Transport                    Core Component
> maintained
> AxisClient                            Core Component
> maintained
> AxisServer                           Core Component
> maintained
> AxisTransport                      Client Transport plugin
> removed
> AxisTransportLibwww         Client Transport plugin
> unmaintained
> AxisXMLParserExpat          XML Paser plugin                    unmaintained
> AxisXMLParserTspp           XML Paser plugin                    unmaintained
> AxisXMLParserXerces        XML Paser plugin                    maintained
> SimpleAxisServer                Server Transport
> maintained
> 
> sanjaya.
> 
> ----- Original Message -----
> From: "Damitha Kumarage" <damitha@opensource.lk>
> To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> Sent: Friday, November 19, 2004 6:46 PM
> Subject: Re: Do we need to keep LibWWW transport updated
> 
> 
> > Hi,
> > I think we should only remove all refrences of unmaintained modules from
> > all   kind of build process(make ,ant, vc). But I prefer keeping the
> > source at cvs for the time being. That might help for interested parties.
> >
> > regards
> > damitha
> > >
> > >
> > >
> > >
> > > +1 for documenting status of modules - where would we do this, though a
> > > cvs
> > > readme  or on the website?
> > >       Is there any way that we can remove libwww entirely from the src
> > > tree
> > > - does cvs allow you to find "deleted files" as some repositories do (I
> > > don't know enough about how cvs works, sorry).
> > >
> > > +1 for build frameworks being updated so they now longer reference
> libwww
> > > at all.
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> > >              "sanjaya
> > >              singharage"
> > >              <sanjayas@opensou
> To
> > >              rce.lk>                   "Apache AXIS C Developers List"
> > >                                        <axis-c-dev@ws.apache.org>
> > >              17/11/2004 04:10
> cc
> > >
> > >
> Subject
> > >              Please respond to         Re: Do we need to keep LibWWW
> > >               "Apache AXIS C           transport updated
> > >              Developers List"
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > A question on infrastructure. The current active developers will know
> what
> > > are being maintained and what are not. But for new people or for the
> sake
> > > of
> > > documenting it should we put it down somewhere as to the current status
> of
> > > each module (i.e. whether they are being maintained or not) or is this
> > > overkill?
> > > Also what should be done for build frameworks (i.e. vc, ant, make) for
> > > unmaintained modules? For example should we remove the libwww transport
> > > project from the Distribution workspace (while keeping the vc projects
> if
> > > needed later)?
> > >
> > >
> > > +1  for hibernating libwww transport.
> > >
> > > sanjaya.
> > >
> > > ----- Original Message -----
> > > From: "John Hawkins" <HAWKINSJ@uk.ibm.com>
> > > To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> > > Sent: Monday, November 15, 2004 4:00 PM
> > > Subject: Re: Do we need to keep LibWWW transport updated
> > >
> > >
> > >>
> > >>
> > >>
> > >>
> > >> +1
> > >>
> > >>
> > >> John Hawkins
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>              Samisa Abeysinghe
> > >>              <samisa_abeysingh
> > >>              e@yahoo.com>
> > > To
> > >>                                        axis-c-dev@ws.apache.org
> > >>              15/11/2004 05:00
> > > cc
> > >>
> > >>
> > > Subject
> > >>              Please respond to         Do we need to keep LibWWW
> > > transport
> > >>               "Apache AXIS C           updated
> > >>              Developers List"
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Hi All,
> > >>     I have done some major improvements to axis2 transport over the
> past
> > >> couple of weeks (e.g.
> > >> cookie support and keep alive support etc.)
> > >>
> > >>     I did not update the LibWWW transport in line with those changes.
> > >>     I feel that it is a burden to keep updating LibWWW based transport
> > >> as
> > >> well (unless someone
> > >> voulenteers to do so)
> > >>
> > >>     Hence I have assumed we are only using axis2 transport from 1.4
> > >> onwards. Is that fair enough?
> > >> Thanks,
> > >> Samisa...
> > >>
> > >>
> > >>
> > >> __________________________________
> > >> Do you Yahoo!?
> > >> Check out the new Yahoo! Front Page.
> > >> www.yahoo.com
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Damitha Kumarage
> > hSenid Software International (PVT) Ltd
> >
> 
> 
> 
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 


Mime
View raw message