Hey Nikolai,

Our permissions and authentications are controlled via the
htpasswd/htaccess
utility which is very common to Apache-style web servers.

Could you elaborate more on the single-CGI page architecture?
How do you differentiate pages? (using a main.cgi?Page=12 method?)


Thanks,
Liran.


(Sorry for the top-posting, my email client at work... well, suck for a
lack of a better word).



-----Original Message-----
From: Nikolai Kondrashov [mailto:Nikolai.Kondrashov@...]
Sent: Thursday, November 13, 2008 2:48 PM
To: Liran Tal
Cc: blong@...; David Jeske; ClearSilver@yahoogroups.com
Subject: Re: ClearSilver for C CGI bindings

Liran Tal wrote:
> I would love to hear about other "live" examples implemented in C for
> ClearSilver usage as it's what we are going for.
>
> In regards to the model, we're talking about a configuration for a
> router's settings web application and I was thinking of implementing
it in
> such way that each configuration/status page is a CGI program of it's
own
> with it's own cs template and there will probably be a single hdf file
> which aggregates all the data.
>
> In this manner too, I would be happy to hear of ideas for improvements
> or a "better way to do it" comments.
Well, we're using it exactly for such purpose. Currently our
web-interface
has over a hundred pages and we use it almost to its full potential.
Despite
a few minor issues, ClearSilver is great for such thing. Thanks Brandon
and
others :)!

However, we use different architecture: there is only one CGI program
which
handles authentication, access control, general markup, template
rendering,
navigation and request routing across pages and form processing modules.
This way, when adding another page or form, you only have to worry about
actual form dataset processing/output and markup.

Sincerely,
Nick


********************************************
This outgoing mail message was scanned by McAfee GroupShield Engine