🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>>Then you have to write at least three programs.
> 
> Not necessarily.  CGI is not a requirement.  The webserver can do the
> requested work directly. 

Ok. Three layers then.

> And incidently, even if you want to use CGI, you
> don't need to write a program for it.  Just install the Perl engine from
> http://www.perl.com and then shell out to it when needed.

That would be three programs then.

>>I do not know what ideas you have for a program to be 'web-enabled'.
>>But if your server and the gui-client communicate using sockets and your
>>own protocol, then the sever could be web-enabled already.
> 
> Only if HTTP were being used for that protocol to begin with.

Not needed.
HTTP for browser<->webserver.
CGI for webserver<->cgiapplication.
Own protocol for cgiapplication<->server. (The same as server<->guiclient).

What I meant was "web-enabling the server" by writing a cgiclient for it.

But the intention of my reply was to make it clear to David that
a lot of aspects had to be considered and to invite him to
express his needs more to the point.

Hans.