[racket] my 2 cents on Web application tutorial being too advanced

There are reasons why one might want to write web apps in Racket but
blogging may not be the best use case. I wish TOPSL is maintained up to
date with Racket and featured more prominently.




On Mon, May 5, 2014 at 7:44 AM, Ben <yfefyf at gmail.com> wrote:

> I agree with you on the URL part. When I saw URL like:
>
>
> http://localhost:50937/servlets/standalone.rkt;((%22k%22%20.%20%22(1%201%205404687)%22))
>
> I thought I probably won't write web application like this. Because I
> think URL is part of the content, and it should be meaningful.
>
>
> On Sun, May 4, 2014 at 11:12 PM, J G Cho <gcho at fundingmatters.com> wrote:
>
>> I think the first tutorial (blog) might be better off using
>> http://docs.racket-lang.org/web-server/dispatch.html, which resembles
>> more of the conventional way of doing web app, ie dealing with request and
>> response.
>>
>> In particular, the resulting k-url is not permanent (at least when I was
>> working thru the tutorial a couple of years ago), and it's a bit of a head
>> scratcher that you cannot link to a blog post.
>>
>> The continuation based approach may make more sense (better motivation)
>> in an e-commerce/shopping cart example.
>>
>>
>>
>>
>>
>> ____________________
>>   Racket Users list:
>>   http://lists.racket-lang.org/users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20140505/3b899592/attachment.html>