[racket] More consistent approach to web programming?

On Thu, Oct 7, 2010 at 2:26 PM, Greg Hendershott
<greghendershott at gmail.com>wrote:

>
> On the server side, it's tricky because I obviously wouldn't want to
> rewrite the Racket web server, dispatching, continuations, etc. I'm
> just talking about the "edge" of it that is the user-supplied
> dispatchee procs. Have them take a request this way and provide
> response this way, instead. Maybe this is where the idea gets stuck in
> mud, if were to come down to two bad choices: A bolt-on with too
> inefficient translation, or, going too far into rewriting server guts.
>

The different level of difficulty comes from that you are generating a
request on the client, but trying to parse a request on the server.  If you
focus on just generating a response on the server (or also try to parse the
response on the client), then the two will be roughly on par.

Basically it is harder to parse than to generate.  So I would say having a
translation layer will be the way to go for now, until in the future you are
ready to parse the request yourself, that's when the ol' good RFCs come in
handy.

Cheers,
yc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20101007/61fe08a5/attachment.html>