[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Re: Configuration
Nah.. CPPSERV doesn't claim to support "standards", it claims to have
API losely based on that of J2EE Servlet API ;-)
This means we can (and probably will) invent config format of our own.
In fact XML parser is the last thing I want to
hook up to this engine - it will automatically add dependancy on libs
that are at least ~1.5 M in size. Not something I
want to have in embedded device.
BTW, what do you mean by defining error pages? Isn't that done by
Apache? (ErrorDocument in .htaccess or apache.conf)
So, config-wise - we have session timeouts, "application definitions" -
i.e. set of related servlets sharing ServletContext and
session name. I guess adding per-servlet parameters should be reasonable
(think multiple instances of same servlet
hooked to different databases, etc).
Anything else?
Thibaut Colar wrote:
> Besides servlets definitions ?
> not: much, most common i define is error pages (404)
> and also very useful is session timeout.
> Have rarely used anything else, i f any.
>
> I'm not a big fan of the web.xml myself.
> 1) it's xml ... so you know :-)
> 2) it needs both the definitions, and then the mapping, and on most
> java containers it needs all the definitions first, followed by all
> the mappings, so it's annoying to edit (2 places). But i guess it's
> an implementation issue so you don't have to make yours stupid like
> this :-)
>
> But, i guess you gotta make the web.xml regardless cause it's "standard"
>
> Ilya A. Volynets-Evenbakh wrote:
>
>> I'm thinking about configuration of servlets right now.
>> Ideas on what exactly should be configurable?
>> Should I perhaps use web.xml config format?
>> Question to those who program a lot of servlets:
>> What things have you ever actually configured in real life?
>>
>> All ideas are welcome.
>>
>>
>>
>
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com