> The administration server relays the logic on a SCGI application
> server in which I'm writing all administration logic. In this way,
> we can develop it in a high level language rather than C (write
> Cherokee in C does make a lot of sense, but it sounds crazy to write
> a SCGI server in the same way, doesn't it?)
Not sure how complicated the administration logic is ... if not
that bad, it may also make sense to avoid a stand alone process
(SCGI, FCGI, CGI) at all? For example, the config file can specify
the admin path name ("/admin" by default) and any requests that
ask for content in that path is handled internally, using a
logic that's similar to but simpler than CGI. Or, just plain CGI
in C/C++.
It's definitely more work because it's always easier to build
pages with one of the Python web frameworks. The thing is,
cherokee is very small and lightweight by itself. Python is
much much bigger. The web development frameworks are typically
very big too. If the SCGI is written without using any python
web development frameworks, it's similar to writing a CGI in
C/C++ and you don't get much benefit from Python. You'll still
have to install Python though. Plus, there are some CGI libraries
available for C/C++.
Jack
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
