On 3/6/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-03-06 at 10:14 -0800, Martin Cooper wrote:
> > On 3/6/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > >
> > > On 3/6/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > > >
> > > > (feel free to keep discussing names etc, but for the moment I'm going to
> > > > go ahead with the one above)
> > > >
> > > <snip/>
> > >
> > > But do it within a reasonable time frame (atleast post any objections
> > > to JWC in a week -- I think thats reasonable, unless anyone wants more
> > > time?). I have been meaning to add some initial components to JWC and
> > > begin work there, and while I agree that the name is important, this
> > > name game is now getting old ;-)
> > >
> > > Recap - We had 3 votes for JWC in the initial vote thread, and there
> > > seems to have been more added informally on parallel conversations on
> > > commons-dev. Seems the J*C "trend" is catching on (see Stephen talk
> > > about JLC in another thread).
> > >
> > >
> > > > Would anyone like to start putting together a list of constituent parts
> > > > for JWC? Please include a proposal for what will happen to any
> > > subprojects
> > > > left dead by the creation of JWC (ie: Taglibs).
> > > >
> > > <snap/>
> > >
> > > Allow me to informally assemble the beginnings of a roster, hopefully
> > > others can add/remove.
> > >
> > > From Commons:
> > >
> > > * EL (dormant?)
> > >
> > > * FileUpload (active, martinc should confirm interest in moving to JWC)
> >
> >
> > I'm not so sure about this. FileUpload has already cloned some code from
> > HttpClient, and could undoubtedly make use of more. Its purpose is to parse
> > HTTP requests. So I'm actually more inclined to move this to Jakarta HTTP
> > Components, assuming that HttpClient eventually morphs into that. (I thought
> > it had already, but I can't seem to find a JHC anywhere.)
> >
>
> Hello, Martin et al
>
> There's already plenty of code to look at in SVN. We are gradually
> moving toward releasing our first official ALPHA. The preview of the HJC
> web site can be found here:
>
> http://people.apache.org/~olegk/httpcomponents/
>
> May I, however, express my (humble) opinion that some of the Commons
> [FileUpload] code may find a better home in Commons [Codec]. To me, all
> the mime/multipart parsing logic clearly belongs to [Codec]. There are
> plans to factor out all multipart encoding code from Commons
> [HttpClient] and move it to Commons [Codec]
>
> This said, Commons [FileUpload] is welcome to consider joining JHC

i wondered if we wouldn't see a lot of discussions like this.  hard
lines have always been hard to draw.  is it possible to have multiple
associations?  some sort of tagging system, with labels instead of
folders?

> Cheers,
>
> Oleg
>
>
> > * Latka (dormant)
> > >
> > > * FeedParser (possibly? dormant)
> > >
> > > From Taglibs:
> > >
> > > * Reusable Dialog Components (RDC) (JSP 2.0, active)
> > >
> > > * Others per interest (I have little interest in JSP 1.1/1.2 taglibs,
> > > been on 2.0 for a while now)
> >
> >
> > I used to work on the Mailer taglib, but abandoned it when someone else
> > decided to reinvent that as a Mailer2 taglib. That now appears to have been
> > abandoned as well, and never made it out of the Taglibs sandbox. So I'm not
> > sure which, if either, would go to JWC.
> >
> > --
> > Martin Cooper
> >
> >
> > Then there is the question of sandbox. There has been talk about a
> > > Jakarta sandbox, that probably deserves its own thread.
> > >
> > > -Rahul
> > >
> > >
> > > > Hen
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to