I agree with Sam. The Racket way to do something like this is to have standard types and function signatures. Roughly that means using the web-server/http structures for requests and responses and modeling servers as `request -> response`. A few of the internals of the Web server also have `request x connection -> void` functions where you can directly write to the connection, but I think this was a mistake and I should have made the `response`s more powerful earlier to not need that.
Jay On Thu, Mar 3, 2016 at 12:51 PM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> wrote: > On Thu, Mar 3, 2016 at 12:23 PM, Brian Adkins <lojicdot...@gmail.com> > wrote: > > On Thursday, March 3, 2016 at 12:15:27 PM UTC-5, antoine wrote: > >> There is the fastcgi protocol http://www.fastcgi.com/drupal/ (maybe it > >> is underlying rack and wsgi). > >> I have done basic tests with it: > >> http://antoineb.github.io/blog/2015/06/02/basic-fastcgi-with-racket/ > >> > >> I haven't found any racket implementation so far. > >> > >> On 03/03/2016 04:16 PM, Brian Adkins wrote: > >> > Is there anything analogous to Rack (Ruby) or WSGI (Python), i.e. a > standard protocol between web servers and web applications, in the Racket > world? > >> > > >> > http://rack.github.io/ > >> > > >> > https://www.python.org/dev/peps/pep-3333/#abstract > >> > > >> > Thanks, > >> > Brian > >> > > > > > Ah, I remember fastcgi from the early, and painful, days of Rails > deployments - I don't want to go back to that :) > > > > IIRC fastcgi is more about the protocol between a front end web server > and an application server it's proxying to. I'm referring to the > intra-process interface between the code handling the low level http > protocol and the higher level application. > > > > In the Ruby world this would be the interface between Unicorn, Puma, > Passenger, etc. and a Rails application. > > > > Rack wasn't available for early releases of Rails, so it's not something > I *need*, but I also didn't want to be unaware of something that's > fulfilling that role. > > Jay would be able to say more, but there isn't something explicitly > like Rack in the Racket web server. > > Roughly, the `serve/servlet` function talks directly to the web-server > implementation, and the servlet interface is just a `request -> > response` function. You could layer things by composing those > functions -- I think that would be the most Rack-like thing currently. > > Sam > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Jay McCarthy Associate Professor PLT @ CS @ UMass Lowell http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
