"housecat" -- new need, embedded servlet engine

[Aaron Smuts <AS...@therealm.com>]

I need a servlet engine that I can embed in the remote cache.  It must have
a small footprint and be incredibly simple, sort of like Jetty.  Tomcat,
with dynamic class loading and all its nice features, is not a good
candidate.

There's a need and it isn't met in Jakarta, so I guess I'll build it.  

I'm going to make "housecat" a simple, embedded servlet container.  Sounds
like fun.  I really like the name.  It even describes the embedded or to be
containable design requirement.

Ha!

Aaron

Re: "housecat" -- new need, embedded servlet engine

[James Taylor <jt...@4lane.com>]

> Why not just use the HTTP engine in the XML-RPC project? It is essentially
> the same thing...

Good call! 

Speculation: how about going one step further. This is for the remote
cache, right? It looks like you are using servlets to synchronize cache
elements and other state between members of the cache. Might it not be
cleaner and easier to use xml-rpc for this?

-- James


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: "housecat" -- new need, embedded servlet engine

[Jon Scott Stevens <jo...@latchkey.com>]

on 2/11/02 11:24 AM, "Aaron Smuts" <AS...@therealm.com> wrote:

> I need a servlet engine that I can embed in the remote cache.  It must have
> a small footprint and be incredibly simple, sort of like Jetty.  Tomcat,
> with dynamic class loading and all its nice features, is not a good
> candidate.
> 
> There's a need and it isn't met in Jakarta, so I guess I'll build it.
> 
> I'm going to make "housecat" a simple, embedded servlet container.  Sounds
> like fun.  I really like the name.  It even describes the embedded or to be
> containable design requirement.

Why not just use the HTTP engine in the XML-RPC project? It is essentially
the same thing...

-jon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>