Yep. But I kind of like the idea of using a single servlet: it fits with
how i do things anyway. it makes development of portal-style (nasty word)
web pages with multiple 'channels' in the web page easier to develop - eg,
menu channel, main channel, cross-sell channel, blurb channel, all of which
are sub-brokered out to more logic modules by the logic module invoked in
the xtra path info.
actually, i think i'll shut up till i've worked out what i'm talking about
and learned how to say it nice.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 19, 2000 1:56 PM
To: [EMAIL PROTECTED]
Subject: RE: creation of application wide objects
On Tue, 19 Dec 2000, Alistair Hopkins wrote:
> I also have lots of this sort of nonsense.
>
> My planned solution is to have only one servlet. This will act as a
broker
> to load 'logic modules', which are invoked thru' the url with xtra path
> info:
>
> http://myServer/myServlet/myModule?yada=yada&foo=bar
>
> This has lots of potential advantages as all requests to a given webapp
will
> be processed by the same servlet, making many things easier. The myModule
> will then implement an interface/extend functionality of my choosing,
rather
> than being saddled with the servlet spec. The servlet will just load on
> startup, and any application-scope objects ith it.
So why don't you just shortcut this approach:
make a dummy servlet that will load at startup ( is a configuration job)
that instantiates the Application objects.
You don't need a broker (at least not for this problem)
Sloot.
