World: r3wp

Sure!

damned, it does not work in IE at all, can't connect to localhost, 
even via 127.0.0.1, something weird here :-)

same problem.. testapp/sixteen.html boots me back to login.. using 
port 80

XP / FF

IE 7 as well

Yep, something odd it occuring with that file.

when i log in, i get session?: true  user: guest... then running 
testapp/four.html (or 16).. back to login   session?: false  user: 
guest

looks like something is wrong with the session expiration code (changed 
2 days ago, so probably some fresh bugs, never had that problem before).

well, never let pekr in, he will always comlicate situation in a 
negative way :-)

I consider finding bugs as a very positive action ;-)

You can debug my code anytime Petr

:-) I worked as personal tester for Cyphre and Romano few times :-)

but I have no system for testing - I just randomly click here and 
there and look what app does :-)

release early, release often

Terry: Launch Late to Launch Often http://www.burningdoor.com/askthewizard/2007/03/launch_late_to_launch_often.html

I'll add this.. release betas early ...

nice article

Ok, after testing a lot with FF, and finding no bug in Cheyenne, 
I just cleared the browser cache and all history info and...it  started 
working flawlessly ! Very odd, but since I've cleared cache and history 
in FF, I can't reproduce the problem...Pekr, could you try that ?

same prob

in IE 7 too

I've just hit "Clear All" in FF's option panel and it works ok. Try 
clearing cache, forms data, history and cache at least, it should 
work.

cleared it all.. no luck..

Im running the latest test version of Rebol

2.7.5.3.1

bon je vais me coucher, ciao, à demain!

oops wrong channel :-)

Appréciez votre Doc. de repos, vous ont un grand jour en avant de 
vous demain.

Any idea on maximum connections?

Looking good Nenad... the extension modules are the bee's kness.

What's the status of the PHP engine?

Nenad, there doesn't appear to be any session cookie being set after 
logging.. if that helps

In mod-rsp. the session timeout is set to 00:20  .. is that 20 seconds?

(or 20 mins?)

20 minutes

big timeout :-)

what does that mean?

if there is no http activity from the user, they get logged out after 
20 mins if they try another http request?

Nenad.. any chance of editing mods without restarting the daemon?

Right, user are logged out after 20 minutes of inactivity. You'll 
be able to define this timeout value per session (feature not yet 
implemented).

Terry, in theory, you can change anything in Cheyenne without restarting 
it through the RConsole service.

Is it all working now?  No known showstoppers?

but mods have a special loader, so if you want to reload a changed 
module, you need to unload the previous one and do some internal 
cleanup in Cheyenne. This "unload and cleanup" part need to be implemented 
to be able to reload an active module. OTOH, loading a new module 
could be done right now without any issue (remains untested).

Graham: yes, RSP and Session support is fully working, but you should 
consider it beta state.

unload is easy... its the cleaning up part ...  ;)

I didn't had much time to work on an internal API for live changes 
in Cheyenne, but, in theory, you should be able to reload the entire 
Cheyenne and Uniserve engine without restarting and without loosing 
opened connections.

is the clients URL in the req/in/headers  ? tried printing the headers 
to the console, but chokes on the HOST?

oh really.. interesting

This kind of  "change in live" stuff is still experimental.

probe req/in instead

um, which phase contains the clients ip address?