World: r3wp

Carl, did you see our above discussion on getting Cheyenne to shed 
root access, and my request in R3 Chat to have Library access enabled 
in R2/Core?

It's essential for getting R2 up to a professional level for web 
serving

do the latest core have odbc as well?

It doesn't have Library

The 2.7.8 planning seems to include some goals in that direction, 
making View not bomb out when X11 is not running, but the time plan 
was abandoned

rebcmd has odbc, ssl and library access.

Sure, but I need Library in Core to have it be meaningful in Syllable 
Server

So, it's just simply releasing rebcmd as core ....if the will exists

Making the REBOL side process a command-line option for /Core and 
build option for /Command would be a good improvement.

What causes this error?


15/9-02:54:33.067-## Error in [task-handler-4721] : Make object! 
[
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'protected-exec
    arg2: 'code
    arg3: [block! function!]

    near: [protected-exec/event request/parsed/file get in session/events]
    where: 'fire-event
] !

I'm trying to display the login.rsp page of a webapp

the login.rsp is straight from svn

looking at login.rsp...

maybe it's a httpd.cfg error?

From the error message, the error would come from an incorrect event 
definition in %app-init.r

errors like this are usually coaused by error in app-init.r yes

I deleted the app-init.r and still get the error

In fact I didn't have an app-init.r so added one

IIRC, app-init.r is mandatory for a webapp, even if you don't use 
it.

so maybe that was the first issue.

put it back and restarted cheyenne

very odd .. I deleted the comments in on-application-start and it 
works now!

I can only guess that I didn't complete shut down and restart Cheyenne

You should just "Reset Workers", it's enough to reload all the webapps. 
You should also consider running your dev instance of Cheyenne with 
-w 0 command-line option to make it reload all apps on each request.

I'm looking at the code in RSP.r and I can't figure out how you could 
raise such internal error. Can you please describe me the simplest 
way to reproduce that error?

reload all apps on each request?

The first thing I did was create a web app with no app-init.r

When I tried to access the login.rsp page I got that error.

yes, the -w 0 option asks Cheyenne to maintain a pool of 0 worker 
process and launch one only when required (killing it when the request 
is completed). That has the side-effect or "reloading" all webapps 
and cleaning any corrupted data in memory produced by user-scripts.

what impact does that have on performance?

it sounds like it would slow it down to cgi ?

yes, but you use it for the development only, not for production. 
I'm working with big RSP webapps and the slowdown with that option 
is barely noticeable.

oh .. ok

I've removed %app-init.r from %www/testapp in Cheyenne's archive, 
started a fresh Cheyenne session, logged in http://localhost/testapp
and I can't reproduce your error. I only keep receiving this kind 
of (normal) error: 

##RSP Script Error: 

	URL  = /testapp/login.rsp
	File = app-init.r


 ** Access Error : Cannot open /C/Dev/Cheyenne/www/testapp/app-init.r 
	** Where: rsp-script 
	** Near:  [init: load join root %/app-init.r]

I've removed -w 0 option also to mimic your config, I'll try putting 
app-init.r back now.

Still no success in reproducing your error...

I renamed app-init.r in my svn version, started cheyenne and don't 
get any error

looks like the cheyenne I'm using is a build from middle of last 
year

You should get some if you try to use any session object functions 
or access any session/content variables.

mid-2009? That's damn old :-)

it let me run the test rsp script

old .. yeah, but since I haven't had any issues, I don't change the 
server apps

That's usually a good rule.

So, I guess no point trying to produce this error since I am using 
an old server build

Right, there's more than 90 SVN revisions since july-2009...

Is anyone using Cheyenne in an environment where they also use Ladislav's 
INCLUDE? The RSP handler has its own global INCLUDE func, which I 
think will conflict.

I am not, but last time I "felt" an Include conflict, it was very 
easy to resolve, in fact

I'm sure it can be resolved. And if someone else has done it in such 
a way that you and Doc approve, I'll gladly borrow from them. :-)

Gregg: 'include is not used internally by RSP engine, so you can 
freely redefine it, like that for example (not tested but should 
work) :

in %app-init.r :

on-application-start: does [

 set 'rsp-include :include 	;-- use 'rsp-include now for RSP script 
 inclusion

 unprotect 'include	;-- 'include is mark as protected by the RSP engine
	do %include.r 	              ;-- Ladislav's include script
]

So, this is a local 'do and not the '*do ?