One thing I did not do that was in the other cache admin servlet was provide authentication. It seems that since all we are doing basic auth, it can be accomplished just as easily (more easily?) in the container configuration.
I also did remove a little differently. Instead of tokenizing on '_' I just allow multiple key parameters and loop over all of them. I was afraid '_' might be found in a valid key. We can add to this, since it is using velocity, it should be easy to extend it while keeping it clean. If it gets too complex we can implement some generalized action handling (or just jump to turbine). -- jt On Fri, 2002-05-17 at 22:11, [EMAIL PROTECTED] wrote: > jtaylor 02/05/17 19:11:31 > > Modified: . build.xml project.properties project.xml > src/experimental/org/apache/jcs/auxiliary/lateral/http/server > LateralCacheServletReciever.java > src/java/org/apache/jcs/auxiliary/lateral/socket/tcp > LateralTCPListener.java > Added: src/conf JCSAdminServlet.velocity.properties > src/java/org/apache/jcs/servlet JCSAdminServlet.java > JCSAdminServletDefault.vm > Log: > Reintroducing the Servlet interface to the cache. I rewrote it using velocity > which makes the code a little cleaner. I still would like to add a detail page > for viewing the items in the cache and removing one (or perhaps more than one). > Seems like a decent start. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
