On Mon, Jan 14, 2013 at 02:42:40PM +0900, Alex Shinn wrote:
On Mon, Jan 14, 2013 at 1:36 PM, Sungjin Chun chu...@gmail.com wrote:
As far as I know, revised RFC permits UTF-8 characters in the URL without
encoding. Am I wrong here?
Thus you can't use raw non-ASCII bytes in a URI - they must
Hi Matt,
I attempted to use the zmq egg for a while and ran into the same problem. I
did not have the time to debug it too much so I abandoned using it,
although I would like to pick it up at some point in the future.
That being said, I think it is GC/finalizer/memory-leak related. I would
get
On Mon, Jan 14, 2013 at 09:18:52AM +0100, Peter Bex wrote:
On Mon, Jan 14, 2013 at 02:42:40PM +0900, Alex Shinn wrote:
On Mon, Jan 14, 2013 at 1:36 PM, Sungjin Chun chu...@gmail.com wrote:
As far as I know, revised RFC permits UTF-8 characters in the URL without
encoding. Am I wrong here?
I've read the docs several times and searched via google for examples.
I'm sure the answer to this question is staring right back at me but I'm
not seeing it. Using spiffy only, how does one write a super simple
dynamic hello world?
Say for example I have a function that can read values from a
Thank you very much. :-)
My proposed hack(yes, no solution) just works for me but I found that it is
just wrong w.r.t RFC.
I'll try your modification and and let you know whether it works or not.
Thank you again.
On Mon, Jan 14, 2013 at 5:08 PM, Ivan Raikov ivan.g.rai...@gmail.comwrote:
Hi
On Tue, Jan 15, 2013 at 7:35 AM, Sungjin Chun chu...@gmail.com wrote:
Thank you very much. :-)
My proposed hack(yes, no solution) just works for me but I found that it
is just wrong w.r.t RFC.
I'll try your modification and and let you know whether it works or not.
Thank you again.
On
My intention is to create search client for Solr (search server using
lucene); where I should send
request URL like this;
http://127.0.0.1:8983/solr/select?q=삼계탕start=0rows=10
I've tried to create this client using http-client egg and had found that
it does not like UTF-8 characters
in the
On Tue, Jan 15, 2013 at 11:50 AM, Sungjin Chun chu...@gmail.com wrote:
My intention is to create search client for Solr (search server using
lucene); where I should send
request URL like this;
http://127.0.0.1:8983/solr/select?q=삼계탕start=0rows=10
I've tried to create this client using
Hi all,
I realized that I replied only to Sungjin and neglected to include the
mailing list, so let me repeat.
Section 3.1 of RFC 3987 defines a mapping between IRIs and URIs such that
UTF-8 sequences are percent-encoded.
So I implemented a procedure iri-uri, which percent-encodes a UTF-8
Hi again,
I have now extended the utf8 code in uri-generic, so that UTF-8
sequences are percent-encoded as lists of the form '(% h1 h2 [% h3 h4
...])). The percent-decoding routine is not going to decode sequences of
more that one byte, so that now percent encoding normalization will not
On Tue, Jan 15, 2013 at 2:23 PM, Ivan Raikov ivan.g.rai...@gmail.comwrote:
Hi again,
I have now extended the utf8 code in uri-generic, so that UTF-8
sequences are percent-encoded as lists of the form '(% h1 h2 [% h3 h4
...])). The percent-decoding routine is not going to decode sequences
Hi Alex,
I understand your point about make-uri, but I want to provide a uri
constructor that takes a UTF-8 input string and maps it in accordance with
RFC 3986 / 3987.
So we still have to perform path and percent-encoding normalization steps
for the ASCII portions of the string. make-uri
Oops, the second example should have been
For the string 삼계탕 the octets are EC 82 BC EA B3 84 ED 83 95 and
(utf8-string-uri http://example.com/삼계탕;) produces
#(URI scheme=http authority=#(URIAuth host=example.com port=#f) path=(/
%EC%82%BC%EA%B3%84%ED%83%95) query=#f fragment=#f)
Sorry about
Hi Matt,
matt welland m...@kiatoa.com writes:
I'm guessing that with-headers and send-response are where I should
start but not sure how they are intended to work. A trivial hello
world example would be a great help.
you can check this Omelette Recipe from Chicken Gazette, issue 8:
14 matches
Mail list logo
