Yariv Sadan wrote:
> I have been thinking too about how in some cases (as in the Arc
> challenge), it looks like creating the html in the controller using
> function calls or objects (like ehtml) and skipping the view could
> make the code shorter. My current impression -- and I could be wrong
> -- is that Arc style programming works better when most of the content
> is dynamic and that ErlyWeb style works better when you have large
> amounts of static html in which small amounts of dynamic data is
> embedded.
>
> Btw, you can bypass views today by returning {response, [...]}, so
> nothing is preventing you from doing Arc style programming in ErlyWeb.
> You just have to write some library functions for generating html
> entities and maybe add support for continuations in ErlyWeb (this
> isn't too hard).
>
I was think of "unrolling continuations". Unrolling similarly to loop
unrolling in language compilers. One of the problems with continuations
is the amount of memory consumed. I watched a talk off google video by
one of the developers of seaside, sorry can't remember which talk, where
he was asked how much memory was consumed by the use of continuations.
He stated about 2MB per session. He was likely making a "guessimate"
based on he's experience and not base on actual measurements but even so
that's alot. When you consider that for most sites most of the time the
use of continuations is to allow the extra functionality it provides is
unwarranted. Being mostly queries of static data versus editing,
multipart forms and the dreaded shopping cart example. In fact the use
of continuations and the associated session can be annoying. Consider
the seaside tutorial located at
http://www.swa.hpi.uni-potsdam.de/seaside/tutorial. I aim to read about
a page a day, but the session information times out and I have to go
back to the first page before finding my place. Very frustrating. It
would be much better to have this functionality turned off by default
and only turn it on as needed.
Anyway, what I was thinking it might be possible to "unrolling
continuations" in loose terms. Would it be possible to do this is such a
way as to,
1) reduce memory usage
2) be able to turn it on only for a section of code
3) serial to a database such as mnesia, so that,
4) unlike continuations be distributed for the purposes of redundancy
and load balancing.
Can anyone point be to some good references on continuation so that I
can actually get a deep understanding of continuations, etc?
trying to run out the door,
Jeff.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
