<br><div><span class="gmail_quote">On 5/29/07, <b class="gmail_sendername">Jay McCarthy</b> <<a href="mailto:firstname.lastname@example.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">email@example.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Another question, currently the web-server provides bindings as an<br>alist of symbols and strings. This causes problem when non-UTF8 data<br>is sent to the web-server, because it cannot be turned into MzScheme's
strings. Another problem is that it complicates file-content<br>(currently the filename is thrown away by the server.) How to people<br>feel about switching to a list of bindings. Where a binding is either<br>(Binding:Form key:bytes? value:bytes?) or (Binding:File key:bytes?
<br>filename:bytes? content:bytes?). This will avoid both problems.</blockquote><div><br>Hi Jay - <br><br>Do you mean that both the key & the value would be replaced with bytes instead of strings? <br><br>IMHO for files it makes sense to use bytes as the value because often we just want the file raw rather than processing it. But for form bindings it seems string is more useful as it's easier to convert to other types, so to me this doesn't seem to be a better solution.
<br><br>Also - if non utf-8 bytes are difficult to translate to utf-8 at web server level then it's probably also not trivial to do so at servlet level. Are there good mechanisms to handle code page translations in mzscheme?
<br><br>My 2 cents ;) <br><br>yinso <br><br></div></div>