Re: Newbie: Mixing HTML & WO Pages?
Re: Newbie: Mixing HTML & WO Pages?
- Subject: Re: Newbie: Mixing HTML & WO Pages?
- From: petite_abeille <email@hidden>
- Date: Thu, 23 Oct 2003 20:29:39 +0200
Hi Bod,
On Thursday, Oct 23, 2003, at 19:38 Europe/Amsterdam, Bob McCormick
wrote:
Hmmmm - this caching that you mention sounds very promising.
Keep your expectation low as there is a couple of gotchas...
Could you explain a little bit more - or point me to documentation
that explains this?
Such an approach is not specific to WOF, so I don't think there is any
specific documentation for it. But you may want to check the omnigroup
mailing list archives.
Seems like a really good solution as the content for this particular
site isn't changing very frequently at all - just a lot of
WORepetition.
Yes. If your data is more or less stable, such a "mixed" solution could
be beneficial.
Seems I'd either have to load the cache on application startup and
then update the cache if anyone enter new information for a specific
table. Rest of the time, it would be blazing fast. This sounds good.
This is broadly speaking what you will need to do.
Anxious to hear more if you don't mind.
Practically speaking, the idea is to use WebObjects or something
similar to generate the content in the first place, but to vend this
content through a traditional web server (e.g. Apache).
But this requires some work.
First and foremost, you will not be able to use session based component
as you need to take your application name space (aka urls) under your
firm control. This is not as trivial as it sounds...
Assuming that you can come up with a rational (and predictable) name
space for your application, life is good.
Here is one scenario:
Setup a custom error handler in your web server. When the server cannot
resolve an URL, it will invoke your handler. The handler will in turn
request the generation of the content to your dynamic application. The
application will return some dynamically generated content matching the
requested url, store it somewhere accessible to the web server, and
tell the server to vend that content. This is more or less what could
happen during the initial request. All further requests can from now on
be served by the web server directly, without any needs for either the
error handler nor the application to intervene. Of course, you will
need some mechanism to expire/invalidate the generated content when the
need arise. But if you are that far along, this is the last of your
problem ;)
Last but not least, you may need to "shoehorn" WOF into behaving
"properly":
http://www.w3.org/TR/2003/NOTE-chips-20030128/
Cheers,
PA.
_______________________________________________
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.