Re: Picking up .wo changes
Re: Picking up .wo changes
- Subject: Re: Picking up .wo changes
- From: Anders F Björklund <email@hidden>
- Date: Sat, 7 Jun 2003 00:37:28 +0200
Pierre Frisch wrote:
What is the benefit of loading templates from the database ?
(assuming that with "templates" you mean the .wo bundles)
In the application that load from the DB I had to give the web
designer the ability to upload site templates. There is an admin
application that enables you to configure the application and upload
the templates and there is a run time application that display them
for the enjoyment of surfers. Storing them in the DB was the logical
thing to do.
Right. Only wish the web designers I work with could learn WO
components...
(or that the .wo bundles would work better with their graphical tools)
I did some custom tags instead (search/replace stuff) and parse strings.
The one thing to be careful: Your cache must be thread safe.
If I ever want to enable "concurrent requests", you mean ?
Otherwise WebObjects would only be running a single request at a time
anyway, would it not ?
Concurrent request handling is the default behavior in WO 5.x and I
would not bank to much on the ability to disable it. I remember
reading somewhere that WO 5.x is always multithreaded and that you
should never make the single thread assumption.
It is ? I was under the impression that it wasn't, and that you were
supposed to muck around with WOLongResponsePage components? (which
*are* threaded).
A test application I just did in WO 5.2 sets
"WOAllowsConcurrentRequestHandling=false", and
WOApplication.allowsConcurrentRequestHandling returns false?
It does have a "WOWorkerThreadCount=8", but isn't that just for
converting the requests from the adaptor? (behind the scenes, like
garbage collecting)
And it handled each request in sequence, each one waiting nicely for
it's turn (too long wait translates to a dead instance in a wotaskd
deployment scenario)
One can get some really nasty deadlock issues, from unlocked
editingcontexts for instance, so multi-threading isn't that easy to
do...
I recall Apple recommending running several app instances instead (and
buying a few more Apple server boxes while you were at it :-)
Or perhaps I'll just forget about it all, and go back to PHP and
MySQL again...
At least there I can look at the source code, if I wonder about
something.
If you don't care about performance, you don't need caching and all is
simple....
Exactly! (Arguable about the performance, of course)
And for the really basic things there's always CGI...
--anders
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.