Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Tomas, I'm quite upset about your statement that the URL handling in PicoLisp is broken. This is not the case! It proved to be very efficient and useful during more than a decade. http://logand.com/blog/picolisp-behind-nginx-proxy.html This doesn't address José's original issue of encoding

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Hi Alex, http://logand.com/blog/picolisp-behind-nginx-proxy.html This doesn't address José's original issue of encoding sessions into URLs, as it also encodes the port number into the URL. So what is gained? Only the purpose of serving other (static) content? This can be done with the

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Hi Tomas, so 'httpGate' doesn't have enough information about which application the expired port belongs to. This could probably be solved with some more bookkeeping. As far as I can see, your 'nginx' can't handle that either, because it doesn't keep track of session ports related to

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Hi José, http://picolisp.com/53823/59880452264949525~-2-1h.html based on ... And this is why putting session data in the URL is a terrible practice, correct link: http://picolisp.com/5000/-2-1h.html I know your criticism of the URL strategy in PicoLisp, but I don't agree completely with

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Hi Alex, http://picolisp.com/53823/59880452264949525~-2-1h.html based on ... And this is why putting session data in the URL is a terrible practice, correct link: http://picolisp.com/5000/-2-1h.html I know your criticism of the URL strategy in PicoLisp, but I don't agree completely with

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

Hi Tomas, I agree with José, I think the URL handling in PicoLisp is broken. The main purpose of an URL is not to copy/paste it, and usually mistakes like the above one can be easily avoided. Copy and pasting URL is one of the most important features. Copying session-URLs is not

Multiple asynchronous HTTP POSTs and call versus in - a word of warning.

Hi Everyone. New article in the wiki: http://picolisp.com/53823/59880452264949525~-2-1h.html based on today's adventures.

Re: Multiple asynchronous HTTP POSTs and call versus in - a word of

On Tue, 21 Jun 2011 00:33:48 +0700 Henrik Sarvell hsarv...@gmail.com wrote: Hi Everyone. New article in the wiki: http://picolisp.com/53823/59880452264949525~-2-1h.html based on today's adventures. And this is why putting session data in the URL is a terrible practice, correct link: