On 28 November 2010 00:31, YC yinso.c...@gmail.com wrote:
I agree with Neil that xexpr or sxml are very nice representations of html
as well. Given their inherent advantage I think an extensible response
mechanism might work better:
1. create hooks to handle different response types
Hi Jay:
I have a question as to what you refer as backwards incompatible.
Will the old way (bytes response format) be workable since currently my
blog server is setup by using some libs from untyped from planet and I'm
not sure if this change will have any impact to those libs? Thanks,
On Mon, Nov 29, 2010 at 3:41 AM, Nevo sakur.dea...@gmail.com wrote:
Hi Jay:
I have a question as to what you refer as backwards incompatible.
Most Web applications will become contract violators because they are
returning Xexprs directly to send/suspend, etc rather than returning
response
This kind of thing has happened many times for other parts of the
system (the class system is a good example). We have generally tried
to avoid so much breakage and I think we should here. One technique is
to have a new name for the new version (or a new name for the old one
if that is more
4 matches
Mail list logo
