[Seaside] REST and Seaside

[Cees de Groot]

On Tue, 12 Apr 2005 11:47:38 +0400, Dmitry Dorofeev  
<dima-sender-3c337a at yasp.com> wrote:
>>> If we have 'static' pages on the site it would be more
>>> effective to get them from hard drive and not to generate with
>>> Seaside or other dynamic framework.
>>   Not really necessary - first, you'll be surprised how much pages per   
>> second you can dynamically generate. Second, if that's too much load,
>
> I run some tests about 6 months ago with Seaside Sushi Shop.
> Seems like it is 1 or 2 page per second rate on a 1Ghz FreeBSD box.

I wasn't talking about the whole Seaside machinery, just about the dynamic  
page generation.

Anyway, I looked into HttpView2, Seaside, Kom to see whether they can be  
hooked up. I think it can be done, but all three components are, err,  
documentationally challenged ;), so it'll take some fiddling and thus some  
time. My idea is to have a Kom session, an HttpView2 entry point, and some  
sort of glue class that generates callbacks to Seaside, using the current  
Kom session to locate the Seaside session; the latter class could be used  
inside the HV page generation to add jumps into the Seaside part of the  
app from HV pages. The other way around is probably simple.

[Cc'd Goran, not sure whether he hangs around on the "competition"'s list  
(just kidding), he might be interested]