On Mon, 2008-04-28 at 13:38 -0400, Rahul Akolkar wrote: > On 4/28/08, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > > Hi, > > > > we developed a nice little library over at the Excalibur project called > > jnet > > (http://svn.apache.org/repos/asf/excalibur/trunk/components/sourceresolve/jnet/) > > > > It is a common purpose lib that allows you to dynamically register own url > > handlers. Background: the jvm only allows you to set a url handler once, so > > if you want to register handling your own protocols (like webdav: etc.), you > > should be the first one doing so :) Obviously, this might work for > > standalone apps but once you're running in a webapp this is bound to fail. > > > > jnet uses a technique used by other projects to circumvent this restriction > > and allows to register url handlers based on the "current execution > > context", so it's possible to have different handlers for different webapps > > while still running in the same jvm. > > > > The first version is working although this is still a prototype and there > > is room for additions/improvement. > > > <snip/> > > It would be good to describe the scope for these additions / > improvements (especially given that the library is currently small). > See some recent proposals [1],[2],[3] for new sandbox components in > this regard. > > > > As Excalibur itself is not...well...very active anymore and as this is a > > general purpose stuff several projects at Apache (and in other places) could > > benefit from (Cocoon is planning to use it, Felix is definitly another > > candidate although we haven't discussed this yet etc.), commons seems to be > > the right place. > > > > So, my question is if there is interest here and what it would take to get > > this a proper commons project? > > > <snap/> > > A lot of interest isn't necessarily needed to start a component in the > Commons Sandbox. If you don't already have the svn auth, you can get > it by asking for it on this list (you as in, an existing ASF > committer). > > Inclusion into Commons Proper is a slightly different beast. You would > need sufficient community interest (atleast as much as is needed for a > graduation vote to pass). Before that happens, there can be no > releases (none at all out of sandbox).
If the code is already in use in a number of apache projects, then a community shouldn't be hard to gather. Just find one volunteer from each of the projects that use it, or are interested in using it. There is a pretty low bar for committers on existing apache projects to get commit access to commons; a major goal of commons is to centralise code shared between apache projects exactly as you are proposing here. But yes starting in "sandbox" is the usual path. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
