[Erlyaws-list] Fwd: Re: yaws 2.0

[Daniel S. <da...@er...>]

We want to do dynamic page generation and storage of a website/s, but store 
the pages in a database instead of .yaws files in a directory.

So instead of using the part of the url www.website.com/page.yaws to let 
the "page.yaws" content be read from a file - being able to provide a binary 
for processing - providing this as a key to select a page.

Currently yaws does process the file as a binary but you have to go to a lot 
of trouble to change the behaviour of loading this from a db instead of a 
file.

CGI will execute an application.
This will load a .yaws file from a database or other source and process like a 
normal .yaws file.

The reason for this, we supply applications to various entities, and storing 
the webpages in a database will ensure that we can quickly "add" allowed 
pages (which we encrypt in the database) and we can hide certain customer 
specific pages from prying eyes.  All pages are in a "single virtual 
directory"

Doing this by keeping the yaws files in seperate directories can be done but 
gets very inelegant.

Hope this makes it clearer.




On Sunday 25 February 2007 13:24:49 you wrote:
> > I have a feature request :)
> >
> > The ability provide binaries instead of only .yaws files as input for
> > page generation.
>
> Sorry, I'm not clear on what you mean here.
> Can you please give a specific example, or explain how this would differ
> from the CGI facility currently in place for Yaws?
>
> Cheers,
> Julian
>
> > We have been playing around with it - but rewriting yaws with every
>
> upgrade is
>
> > not appealing :)



-- 
-------------------------------------
Daniel Schutte
CEO - Erlang Financial Systems International

Mobile:  +27 84 468 3138
Phone :  +27 11 802 6162

-------------------------------------------------------

-- 
-------------------------------------
Daniel Schutte
CEO - Erlang Financial Systems International

Mobile:  +27 84 468 3138
Phone :  +27 11 802 6162