On Tue, 9 Jun 2009, Joost van der Sluis wrote:
Op maandag 08-06-2009 om 15:28 uur [tijdzone +0200], schreef Michael Van
Canneyt:
On Mon, 8 Jun 2009, Joost van der Sluis wrote:
Op maandag 08-06-2009 om 14:05 uur [tijdzone +0200], schreef Michael Van
Canneyt:
I'm still thinking about adding an option to the apache-modules and fcgi
to let the TWebModule stay in memory, as some kind of session with a
timeout. That would add a lot of other possibilities.... (more
servlet-like)
I've thought about it, and a design as Remobjects uses would be good:
You'd need a global TWebmoduleFactory which is in charge of creating
the instances or picking them from an in-memory pool. Depending on the
application you can create descendents:
- TOnShotWebmoduleFactory (create& destroy a module per request)
- TPooledWebModuleFactory (have a pool of twebmodule instances and route the
request to one of them)
- TSessionWebmoduleFactory (same module throughout the session)
It would require a minor change to the TWebApplication object: it no longer
creates the webmodule directly, but asks the factory to create one.
Depending on which factory is used in the application, one of the above
systems is then used to return an instance.
Yes, something like that
What helps when you have a project you want to work on. So you discover
what features you miss. Do you have an idea for something usefull?
Rework the contributed units section of the FPC website ? :-)
I knew you would say that.
I have some more ideas, but they are not useful for you :(
Another idea is the testsuite website. It could use some polishing,
and maybe even some new sections.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
