6 Jul
2011
6 Jul
'11
6:47 p.m.
Can you test without Hunchentoot, like this?
(with-input-from-string (s your-string) (cxml:parse-stream s (cxml-dom:make-dom-builder))
You could also capture whatever hunchentoot is returning via raw-post-data in a special variable to compare it with your expected data. It should be easy to determine if the issue falls within Hunchentoot or cxml.
It's been a while since I've done any network stuff with Flash, but I remember that it terminates messages with a null byte. Make sure you aren't missing that when you test.
-austin
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
On Wed Jul 06 18:10 , Oleg Sivokon wrote:
> Hi Hans, thanks for reply. The client is Flash, I'm pretty confident about
> the content (I could trace it with tcpdump, so that's not the issue). I've
> also tried (cxml:parse-octets (hunchentoot:raw-post-data :request
> hunchentoot:*request* :force-binary t), and it worked just as I would expect
> it. So it's either CXML is doing something strange with the stream, or I'm
> supposed to do something with the stream before (or after) giving it to
> CXML, or there's a chance something isn't right with stream produced by
> Hunchentoot.
> So, would you have an idea of how would I verify that? It's not really a
> life and death issue, since I believe I could survive with string instead of
> stream, but just to educate myself, I'd like to know :)
>
> Thanks.
>
> Oleg
> _______________________________________________
> tbnl-devel site list
> tbnl-devel@common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel