Re: Servlet Filters Proposal
[EMAIL PROTECTED] wrote: On Tue, 12 Feb 2002, Glenn Nielsen wrote: I have started putting together a proposal for Jakarta-Filters. Once this effort has been bootstrapped in jakarta-commons-sandbox this can be proposed to the PMC as a top level project if enough interest exists. If you are interested in contributing to Servlet Filters please read the proposal below and send me your comments. Let me know if I missed any filters or committers. I'm not sure a top level project is such a good idea. I know we have a jakarta-taglibs already, but maybe it's a better idea to first see if there is enough interest and enough real activity in jakarta-commons. From sandbox to top level project is a bit too much :-) I would be +0 for a top level project that would deal with 'extensions' or 'modules' - i.e. servlet filters, ant tasks, axis handlers, tomcat valves and interceptors, etc. Especially if the organization would be similar with commons. But even for that - jakarta-commons is a much better place, and if it gets so much contribution it overwhelms commons, it's easy to move. The latest proposal defers the decision on whether Servlet Filters gets promoted from the jakarta-commons-sandbox to jakarta-commons or a top level project until after it has been made public in the sandbox and there has been a few months to build a community. At this time it is too early to determine the best place for the Servlet Filters to reside on the Jakarta site. Regards, Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Servlet Filters Proposal
I have started putting together a proposal for Jakarta-Filters. Once this effort has been bootstrapped in jakarta-commons-sandbox this can be proposed to the PMC as a top level project if enough interest exists. If you are interested in contributing to Servlet Filters please read the proposal below and send me your comments. Let me know if I missed any filters or committers. As I have time I will work on setting up jakarta-commons-sandbox/filters using the build and organization pattern from the Jakarta-Taglibs Project. Once we have a build framework setup we can start adding filters. Regards, Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Fwd: Servlet Filters Proposal]
Glenn, I've started working on getting my filters ready for submission, but am not sure which package they belong in. In the PROPOSAL you state The proposed package name for servlet filters is org.apache.servlet.filters..., but if this is in Commons shouldn't it be org.apache.jakarta.commons.filters ? Lance --- Glenn Nielsen [EMAIL PROTECTED] wrote: Here is the link: http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/filters/PROPOSAL.html __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [Fwd: Servlet Filters Proposal]
And filters is very generic too! What about org.apache.jakarta.commons.servlet.filters or something like that? (There must be something better than servlet.) Have fun, Paulo Gaspar -Original Message- From: Lavandowska [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 4:58 PM To: Jakarta Commons Developers List Subject: Re: [Fwd: Servlet Filters Proposal] Glenn, I've started working on getting my filters ready for submission, but am not sure which package they belong in. In the PROPOSAL you state The proposed package name for servlet filters is org.apache.servlet.filters..., but if this is in Commons shouldn't it be org.apache.jakarta.commons.filters ? Lance --- Glenn Nielsen [EMAIL PROTECTED] wrote: Here is the link: http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/filters/PROP OSAL.html __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Fwd: Servlet Filters Proposal]
On Tue, 12 Feb 2002, Glenn Nielsen wrote:
Date: Tue, 12 Feb 2002 10:24:52 -0600
From: Glenn Nielsen [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Subject: Re: [Fwd: Servlet Filters Proposal]
I didn't put commons in the package name because some
feel that commons isn't a good fit for servlet filters,
and this may become a top level project if there is
enough interest.
I agree that having servlet.filters in the package
name is pretty generic, but it is an apt and easy
to remember package name. Especially since the
package name will need to be configured in the
web.xml file.
So far suggested package names are:
org.apache.servlet.filters.{filter-name}
org.apache.commons.filters.{filter-name}
org.apache.jakarta.commons.servlet.filters.{filter-name}
While it's in the sandbox (or in jakarta-commons if it gets promoted), the
base package name really needs to follow the Commons conventions (i.e.
org.apache.commons.filters for a package named Filters). If this is
ever promoted to a full-fledged Jakarta package like Taglibs, it will need
to be repackaged -- this is what happened to Cactus when it was promoted.
Is there really a need for sub-packages for individual filters? Nearly
all of the ones proposed so far are single classes, so having them
together would seem reasonable -- this is how commons-collections is set
up, and doesn't seem to cause any grief. For Filters that require some
supporting classes (or where there is a set of Filters that might be used
together), a subpackage is reasonable.
I don't see a need for servlet.filters versus filters -- the proposal,
and the Javadocs once we have some code -- make it very clear that these
are filters in the Servlet 2.3 sense of the word (i.e. they all implement
javax.servlet.Filter).
Any other suggestions?
Regards,
Glenn
Craig
Paulo Gaspar wrote:
And filters is very generic too!
What about
org.apache.jakarta.commons.servlet.filters
or something like that?
(There must be something better than servlet.)
Have fun,
Paulo Gaspar
-Original Message-
From: Lavandowska [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 4:58 PM
To: Jakarta Commons Developers List
Subject: Re: [Fwd: Servlet Filters Proposal]
Glenn,
I've started working on getting my filters ready for submission, but am
not sure which package they belong in. In the PROPOSAL you state
The proposed package name for servlet filters is
org.apache.servlet.filters..., but if this is in Commons shouldn't it
be org.apache.jakarta.commons.filters ?
Lance
--- Glenn Nielsen [EMAIL PROTECTED] wrote:
Here is the link:
http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/filters/PROP
OSAL.html
__
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
--
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [Fwd: Servlet Filters Proposal]
My only concern is that we end up having an idea for some
other type of filter, not web servlet related and maybe
even more generic. Then having Servlet filers in a
o.a.j.commons.filters will get confusing.
Lets also consider that the official Servlet 2.3 filter
interfaces are placed in the javax.servlet package and
not at javax.filters.
BTW, I would not mind
org.apache.jakarta.commons.servlet
but this would be ok for other web-server related
components too.
Have fun,
Paulo Gaspar
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 5:40 PM
To: Jakarta Commons Developers List
Subject: Re: [Fwd: Servlet Filters Proposal]
On Tue, 12 Feb 2002, Glenn Nielsen wrote:
Date: Tue, 12 Feb 2002 10:24:52 -0600
From: Glenn Nielsen [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List
[EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Subject: Re: [Fwd: Servlet Filters Proposal]
I didn't put commons in the package name because some
feel that commons isn't a good fit for servlet filters,
and this may become a top level project if there is
enough interest.
I agree that having servlet.filters in the package
name is pretty generic, but it is an apt and easy
to remember package name. Especially since the
package name will need to be configured in the
web.xml file.
So far suggested package names are:
org.apache.servlet.filters.{filter-name}
org.apache.commons.filters.{filter-name}
org.apache.jakarta.commons.servlet.filters.{filter-name}
While it's in the sandbox (or in jakarta-commons if it gets promoted), the
base package name really needs to follow the Commons conventions (i.e.
org.apache.commons.filters for a package named Filters). If this is
ever promoted to a full-fledged Jakarta package like Taglibs, it will need
to be repackaged -- this is what happened to Cactus when it was promoted.
Is there really a need for sub-packages for individual filters? Nearly
all of the ones proposed so far are single classes, so having them
together would seem reasonable -- this is how commons-collections is set
up, and doesn't seem to cause any grief. For Filters that require some
supporting classes (or where there is a set of Filters that might be used
together), a subpackage is reasonable.
I don't see a need for servlet.filters versus filters -- the proposal,
and the Javadocs once we have some code -- make it very clear that these
are filters in the Servlet 2.3 sense of the word (i.e. they all implement
javax.servlet.Filter).
Any other suggestions?
Regards,
Glenn
Craig
Paulo Gaspar wrote:
And filters is very generic too!
What about
org.apache.jakarta.commons.servlet.filters
or something like that?
(There must be something better than servlet.)
Have fun,
Paulo Gaspar
-Original Message-
From: Lavandowska [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 4:58 PM
To: Jakarta Commons Developers List
Subject: Re: [Fwd: Servlet Filters Proposal]
Glenn,
I've started working on getting my filters ready for
submission, but am
not sure which package they belong in. In the PROPOSAL you state
The proposed package name for servlet filters is
org.apache.servlet.filters..., but if this is in Commons shouldn't it
be org.apache.jakarta.commons.filters ?
Lance
--- Glenn Nielsen [EMAIL PROTECTED] wrote:
Here is the link:
http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/filters/PROP
OSAL.html
__
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
--
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Servlet Filters Proposal]
Lance, I'm not sure how far along your cache filter is, but I wrote one based on OpenSymphony's OSCache system (www.opensymphony.com) and it works rather well. Much of the heavy lifting was already done by the OSCache engine as it was initially built for a JSP tag library, so most all of what I had to do was improve some threading issues and get the cache to support binary content and additional response information (like content type and content-length). Let me know when you have some code to share, and I'll be happy to look and maybe help a bit. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ - Original Message - From: Glenn Nielsen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 12, 2002 8:37 AM Subject: [Fwd: Servlet Filters Proposal] Here is the link: http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/filters/PROPOSAL.html -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
