World: r3wp

For this I see several options:

1. Somehow load this file as an RSP file and have it processed.

2. Somehow load this file as a SHTML file and have it processed as 
SSI file.

3. Add some marks and inser the stuff on the fly before delivering 
it.

Option 3 has the advantage, that I stay in my running RSP file context. 
On the other hand it's the "handmade" approach.

I'd say your RSP script should "be" the resulting web page; that's 
the normal way to generate dynamic pages. Why do you think of them 
as separate?

I use RapidWeaver to generate some files. And I need to inject HTML 
in one of these generated files. Hence options 1 to 3. The RSP is 
not generating the whole answer page.

Robert, see RESPONSE/FORWARD in the RSP API Reference page.

<% response/forward %payment/index.rsp %>

Q1 - WORDS dialect : this dialect allow defining new config keywords 
that can be used in the %httpd.cfg file for your mod. IN defines 
the config file sections where it can apply. Possible values are 
:
- globals : global config block used for server-wide options
- main : applies to a domain or webapp context
- location / folder : reserved for future use.

Q2 : The REQ argument is set to the current request object. If you 
get none instead of an object!, you've probably messed up something 
in Cheyenne/UniServe internals.

Q3 : Not yet. It's a planned feature that I need also to add a simple 
CRON-like task scheduler inside Cheyenne. Feel free to add your own 
in your mod, I don't that I'll have time to work on it before middle 
summer (low priority task).

thanks... wrt CRON... when you release the next version, I could 
drop that into it and send it back to you.  you don`t have to do 
everything yourself   :-D

I'd like to not do everything by myself, but it's not that easy. 
I have some deep concerns for Cheyenne core part such as speed, memory 
usage, stability and security. Cheyenne has become a *critical* part 
of our business, I have to garantee that a new version won't break 
our webapps in production, nor make them instable, insecure or noticeably 
slower. My responsibility also extends to other companies that are 
selling products or services based on Cheyenne.


I've already accepted small patches on Cheyenne core in the past, 
but it takes me a lot of time to study and test each line of code 
an rewrite them if required. If your code has only a local impact, 
I might use it, if it needs to patch a lot of parts of Cheyenne/UniServe, 
I probably won't. Anyway, you can send it to me, it's always a good 
inspiration to see how other developers solved some specific problem.

I can't disclose much right now, one of our Cheyenne based product 
is getting a lot of attention recently and in a couple of weeks, 
we will know if we need to hire a few more peoples at Softinnov. 
;-)

congrats

Actually what sort of Cheyenne apps are out there?  I don't think 
I know of any ...

Most of Janko's new products are Cheyenne based.

I don't think they're finished ...

Part of Will's company main product is using Cheyenne.

didn't know that ...

I thought he worked for a company .. didn't realise Rebol was important 
in that way.

A few small intranet apps in a couple of TOP 5 french company are 
using Cheyenne and RSP.

Sorry, yes it's for the company Will is working for.

I did release my Hylafax web portal which I know a few people are 
using :)

And we have also a big product using Cheyenne/RSP with already a 
few dozens customers.

what does it do?

I prefer to keep it "under the radar" for a few more weeks. ;-)

who's radar?

Microsoft?  :)

I'd like it would be *that* big. :-)

I did build a web portal to my medical database .. but too busy to 
keep that going.  Have to learn a lot more jQuery ....

Still, I have a few users of that as well.

that's what I use for filling in Acrobat forms programmatically.

So, that's you, me, will .. possibly Terry.  Anyone else?

I see Cheyenne as a web-window to REBOL apps.

what does that mean?

I build REBOL apps, databases, UIs, scripts. If I want some kind 
of web access to that, Cheyenne is key. I don't see Cheyenne as just 
another web server.

I have been loath to push Cheyenne much because of the freezing I 
was seeing before.

Dockimbel, let's say R3 was done and most bugs were squashed, would 
you then build Cheyenne for R3 and would it be from scratch?

the inability to run more than one Cheyenne server at the same time 
has been a problem too.

I didn't saw such "freezing" since september 2008 (the last one that 
happened here). I guess that the last fix about IE POST issue was 
the last possible cause of such problem.

I don't see it anymore because now I use a Rebol client to access 
Cheyenne and not a web browser.

R3: when it will be feature complete and in final beta stage, sure 
I will. I'll probably rewrite complety the lower level networking 
code and try to keep as much as possible the higher level code.

what role would uniserve play, if networking is completely async 
and threading is possible in R3?

UniServe is a thin framework layer other the raw port! stuff. It 
provides an event-oriented framework for implementing server or client 
side protocols. Some UniServe events are same as the lower async 
ones : on-connect, on-close. Other are higher level such as : on-receive 
(trigger when a given amount of data or a given sequence is received).

Did I mention I'd like to see a zope clone one day :)

response/Forward: This looks good. from the docs I see that it's 
possible to forward to a new RSP page. Will this work with a SHTML 
page as well?

did you mean ssi ?

graham, you can run MANY cheyenne servers on the same system .  and 
they can be handling several thousand requests / hour each without 
failure.  


at my client cheyenne is probably the most stable server application 
they have, a part from apache.

UniServe still has a purpose in R3, but it implementation will be 
much lighter and it will run much faster. Btw, one of UniServe's 
plugin, Task-master, is in charge of running and exchanging data 
with external processes given true multitasking abilities to UniServe's 
based products (RSP scripts are evaluated in such helper processes). 
R3 multithreading will make multitasking much simpler and way much 
faster.

Robert: never tried, but as it loops over the whole HTTPd request 
processing pipeline, I think it should work with SHTML.

the mod for access refusal is finished btw.  it works really well, 
I ended up doing it in a mod and doing a few invisible actions within 
the make-response and task-done callbacks.