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
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 t
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 s
Hi Jakob,
> It would be better if the Wiki detected a session URL and fell back to
> the original page.
exactly;-) Long time ago I described my set up to Henrik, see
http://logand.com/blog/picolisp-behind-nginx-proxy.html
As Alex uses home grown proxy called httpGate, it would need to be
probabl
On Tue, Jun 21, 2011 at 11:26:20AM +0200, Alexander Burger wrote:
>
> It would be cleaner if I removed that log in / log out mechanism. Then
> the "home" site would be only for viewing, browsing etc, and the "wiki"
> site allows to log in and modify things.
It would be better if the Wiki detected
On Tue, Jun 21, 2011 at 10:28:53AM +0200, Alexander Burger wrote:
> > ago. This fallback might have to be application specific thing so maybe
> > the wiki software is broken from this point of view, not sure.
>
> Yes, I simply used the existing mechanisms, though a wiki is not a
> typical applica
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
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
> comple
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
On Tue, 21 Jun 2011 00:33:48 +0700
Henrik Sarvell 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: http://picolisp.com/
10 matches
Mail list logo