What libraries we need Lassi Kortela (07 Apr 2019 08:55 UTC)
|
Re: What libraries we need
Peter Bex
(07 Apr 2019 09:31 UTC)
|
URI/URL handling
Lassi Kortela
(07 Apr 2019 10:11 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 10:56 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 12:03 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 12:46 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 14:20 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 15:06 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 15:39 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 15:52 UTC)
|
Re: URI/URL handling
Peter Bex
(07 Apr 2019 16:03 UTC)
|
Re: URI/URL handling
Lassi Kortela
(07 Apr 2019 16:30 UTC)
|
Re: URI/URL handling
Arthur A. Gleckler
(09 Apr 2019 21:06 UTC)
|
Re: What libraries we need
Arthur A. Gleckler
(09 Apr 2019 20:49 UTC)
|
Thank you to Arthur for making a mailing list for us. I put the link to the list archive, https://srfi-email.schemers.org/schemeweb on the front page of https://github.com/schemeweb under the heading. Hope it's OK. I made a new page on the wiki to plan how we should factor this web stack into individual libraries: https://github.com/schemeweb/wiki/wiki/What-libraries-we-need - Do you find anything missing? - Do you disagree about something? IMHO a good starting point (taking a page from many other languages) is to have the request handler abstraction as a divider. So there are libraries that work "above" the request handler level, dealing with individual requests and their details (URL parsing and routing, logging/monitoring/error catching middleware, HTML/XML/JSON, anything dealing with CSS and JavaScript). And then libraries "below" that level for HTTP parsing, sockets, crypto and the like.