World: r3wp

It's not that hard to write one, the hard part is to correctly set 
the execution order for each callback (each module competes with 
all other modules for a given callback event, and you have only 3 
possible positions, 'first, 'normal (middle) and 'last.) The loading 
order of modules in the config file (httpd.cfg) also impact the final 
order of callbacks execution. I plan to move to a much more simplier 
system for Cheyenne 2.0, it will loose some little flexibility, but 
it will be much more easier to write extension modules. But , that's 
long-term, i need first to reach 1.0 ;-).

I think the biggest issue I had was encapping that worked when I 
included my service

I would be curious as to any benchmarks as well.  Why use Apache 
if Cheyenne is faster?

I've fixed some issues in encapping in this new release, i just need 
to document them.

My plan all along has been to incorporate all of our Rebol tech into 
a single unified system, with Cheyenne as the platform.

Basically, you just need to look at cheyenne.r and add an entry in 
the set-cache block, then add a : do-cache uniserve-path/services/your-service.r 
before calling uniserve/boot.

does #include %cheyenne.r works for you ? (never tested here)

(btw, your service don't need to be located in uniserve/services, 
it can be anywhere)

can't remember.. been awhile

Watch out in the rsp.html doc file, the "Session Object" table is 
correct, but all the detailled explanations for the session properties 
are incorrect (coming from the old and obsolete API). Sorry for that, 
it will be fixed in the final release of this document tomorrow.

I have access to FreeBSD boxes (or will have access very soon), so 
I can encap it. I think Jaime may be able to do this as well.

We also plan, at Softinnov, to release it as debian package. The 
issue here is the dependency on rebol binaries, it's a pity that 
there's no REBOL packages that you can "apt install"...

Should we push for mysql:// and Cheyenne to become part of Core 2.7?

(just did)

heh, I have got crash with latest version:

[uniserve] Async Protocol FastCGI loaded
[uniserve] Starting task-master...
[uniserve] Starting HTTPd...
make object! [
    code: 312
    type: 'script
    id: 'cannot-use
    arg1: 'add
    arg2: 'time!
    arg3: none
    near: [time: time + port/timeout
        if
    ]
    where: 'close-expired
]


I run Apache on port 80, so I changed httpd to 8080 ... sinmple CGI 
works, I logged into application OK, simple page worked, 4 RSP test 
crashed with above error ...

I prefer the REBOL binary to remain small. I should put a mysql.r 
and cheyenne.r file somewhere on my website and give out the URL, 
so you could just : do http://.../mysql.rto install and run it.

Sixteen.html gets me back to login screen - is that correct?

Yes, if you're in the /testapp webapp and if your sessions expired.

hmm, should those expire? I just follow your latest release .... 
there is /testapp, I click it, first demo works, but 4 and 16 ASP 
don't ... correct?

followed the same path, ok here...what OS are you using ?

Maarten - Cheyenne part of Core 2.7? Not sure it is OK with Carl, 
especially when RT proposes rebservices (which is a bit different 
concept, but ....)

WinXP Professional, latest patches. I run it just from Total Commander 
by pressing enter on Cheyenne.r It runs on 8080 port, everything 
seems to be OK, except random timeouts, as they were present in the 
past. Now with 4RSP demo I got at least first session frame OK, then 
it crashed imediatelly with above error ...

rebol/version 1.3.2.3.1

looks like your running the old uniserve version, let me look at 
the archive to see if it's my fault...

Now I got the same error even when pressed enter to log-in. Maybe 
some weird stuff on my machine, but Apache was running OK. I ended 
Apache and turned Cheyenne back to port 80.

Nope, it's my fault, the uni-engine.r file in the archive is an old 
version. Give me 2 minutes, I'll update the archive.

ok, thanks a lot ...

Cheyenne v0.9.10.0 re-released due to a wrong version of the %uni-engine.r 
file. Sorry for that. Download link: http://softinnov.org/tmp/cheyenne-r09100.zip

Petr, I didn't had issues with running Cheyenne on ports <> 80. Please 
try it again on 8080 and report me any errors.

http://localhost/sixteen.html

Error Code :  	312
Description : 	script error !
Cannot use path on none! value
Near : 	[prin session/content/hits txt 256 280]
Where : 	protected-exec

now it does not crash, running it on 8080 port. sixteen.html gets 
me back to login screen, 4 RSP demo runs.

Pekr: is your browser accepting cookies ?

of course it is ... well, I hope so :-) If 4RSP works, then it should 
be, no? Wait a min, will try with IE, maybe some FF extension does 
it ...

Terry: normal RSP error, there's no session started, and no 'hits 
variable in session. I should have removed this file from there. 
Its clone in /testapp should work well, once you've logged in.

Pekr, you're right, there's something odd with FF on the sixteen.html 
file.

Doc - do you want cool Systray support? Works excellently.  Dony 
by Cyphre for me, BSD ....

taskbar icon is not too pleasant ...

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 :-)