I prefer not to become a commons component (not that I have something against commons though). The best match seems to be httpcomponents and even though the server component isn't much alive at this stage, we don't need to split up the client & server code, which in case of commons we need to do that.
And another reason : the goal of all codebases in the new TLP will be the same : http and it's extensions and will definitely create a big enough project (PMC Members & committers) to not get into trouble when someone becomes inactive.. Mvgr, Martin Oliver Zeigermann wrote: > Merging the webdav client into httpclient sounds like the best idea to me. > > If this does not work for any reason, it might be an option to move > the webdav client to vfs commons. Or maybe a new commons component? > > Oliver > > 2007/6/3, Martin van den Bemt <[EMAIL PROTECTED]>: >> Hi everyone, >> >> Will do an official proposal in a couple of weeks, but to be able to >> give you some thinking time : >> >> Merge httpcomponents & slide.. >> >> - The webdav client is based on httpclient >> - Merging the 2, will give (more than) enough people on the PMC >> (including me) >> >> Thoughts ? (please keep both lists in the loop where possible). >> >> Mvgr, >> Martin >> >> >> --------------------------------------------------------------------- >> 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]
