Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #56723 > unrolled thread

can forth work with scgi? the faster cgi?

Back to article view | Back to comp.lang.forth

Contents

  can forth work with scgi? the faster cgi? gavino himself <jackvanc3@gmail.com> - 2017-04-04 10:53 -0700
    Re: can forth work with scgi? the faster cgi? Julian Fondren <julian.fondren@gmail.com> - 2017-04-04 11:07 -0700
      Re: can forth work with scgi? the faster cgi? Darin Murphy <murphy.darin@gmail.com> - 2017-04-04 18:25 +0000
        Re: can forth work with scgi? the faster cgi? gavino himself <jackvanc3@gmail.com> - 2017-04-04 15:18 -0700
          Re: can forth work with scgi? the faster cgi? Darin Murphy <murphy.darin@gmail.com> - 2017-04-05 01:52 +0000
        Re: can forth work with scgi? the faster cgi? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-04-05 14:57 +0000
          Re: can forth work with scgi? the faster cgi? Darin Murphy <murphy.darin@gmail.com> - 2017-04-05 18:41 +0000

#56723 — can forth work with scgi? the faster cgi?

or naaaaaa?

[toc] | [next] | [standalone]

#56724

On Tuesday, April 4, 2017 at 12:53:52 PM UTC-5, gavino himself wrote:
> or naaaaaa?

You have two options: CGI or your own HTTP server (alone or behind
another).  FastCGI and SCGI and probably every other *CGI are just
disguised versions of the second option. Instead of implementing HTTP
you implement NotHTTP, with NULs instead of newlines!

SCGI has the small benefit of being documented, unlike FastCGI where
every specification link points to http://www.fastcgi.com/ , but it
shares the lack of benefit vs. just directly implementing HTTP.

[toc] | [prev] | [next] | [standalone]

#56727

Julian Fondren wrote:

> On Tuesday, April 4, 2017 at 12:53:52 PM UTC-5, gavino himself wrote:
>> or naaaaaa?
>
> You have two options: CGI or your own HTTP server (alone or behind
> another).  FastCGI and SCGI and probably every other *CGI are just
> disguised versions of the second option. Instead of implementing HTTP
> you implement NotHTTP, with NULs instead of newlines!
>
> SCGI has the small benefit of being documented, unlike FastCGI where
> every specification link points to http://www.fastcgi.com/ , but it
> shares the lack of benefit vs. just directly implementing HTTP.

Oh  Bernd Paysan created a web-server I believe in Gforth:

https://bernd-paysan.de/httpd-en.html

Which I believe evolved into Net2o:

https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md

Take care now,

Darin Murphy

[toc] | [prev] | [next] | [standalone]

#56732

On Tuesday, April 4, 2017 at 2:25:13 PM UTC-4, Darin Murphy wrote:
> Julian Fondren wrote:
> 
> > On Tuesday, April 4, 2017 at 12:53:52 PM UTC-5, gavino himself wrote:
> >> or naaaaaa?
> >
> > You have two options: CGI or your own HTTP server (alone or behind
> > another).  FastCGI and SCGI and probably every other *CGI are just
> > disguised versions of the second option. Instead of implementing HTTP
> > you implement NotHTTP, with NULs instead of newlines!
> >
> > SCGI has the small benefit of being documented, unlike FastCGI where
> > every specification link points to http://www.fastcgi.com/ , but it
> > shares the lack of benefit vs. just directly implementing HTTP.
> 
> Oh  Bernd Paysan created a web-server I believe in Gforth:
> 
> https://bernd-paysan.de/httpd-en.html
> 
> Which I believe evolved into Net2o:
> 
> https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md
> 
> Take care now,
> 
> Darin Murphy

interesting...
https://fossil.net2o.de/net2o/wiki?name=net2o

[toc] | [prev] | [next] | [standalone]

#56736

gavino himself wrote:

> interesting...
> https://fossil.net2o.de/net2o/wiki?name=net2o

I think so too, though I have a long way to go before I understand it
completely. Take care now,

Darin Murphy

[toc] | [prev] | [next] | [standalone]

#56752

Darin Murphy <murphy.darin@gmail.com> writes:
>Oh  Bernd Paysan created a web-server I believe in Gforth:
>
>https://bernd-paysan.de/httpd-en.html
>
>Which I believe evolved into Net2o:
>
>https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md

No, net2o is not a web server, it's a replacement for TCP/IP, plus
applications that are built on top of it.

- anton
-- 
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: http://www.forth200x.org/forth200x.html
   EuroForth 2016: http://www.euroforth.org/ef16/

[toc] | [prev] | [next] | [standalone]

#56758

Anton Ertl wrote:

> Darin Murphy <murphy.darin@gmail.com> writes:
>>Oh  Bernd Paysan created a web-server I believe in Gforth:
>>
>>https://bernd-paysan.de/httpd-en.html
>>
>>Which I believe evolved into Net2o:
>>
>>https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md
>
> No, net2o is not a web server, it's a replacement for TCP/IP, plus
> applications that are built on top of it.
>
> - anton

Oops! Sorry. I just skimmed through it. Need to be more careful next
time. Thanks Anton for correcting the misunderstanding.

Take care now,

Darin Murphy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.forth

csiph-web