World: r3wp

Cheyenne Kimball: I often stumbled upon her fan pages searching for 
cheyenne keyword, pretty and talented woman.

Cheyenne's 404 : sounds like a victory scream. :-)

yes it is  :-D

doc, trying to understand the mod  'WORDS  dialect...   I am reading 
its parser, and I still don't get what the 'IN token does.  or what 
options I can use, or even why its needed.

can you give me a few pointers on how and why it should be used?

Q2:  within the mod, requests have a locals value of none, does any 
of the uniserve/cheyenne internals touch this or can I use this at 
will within any module, creating an object and appending/changing 
 attributes as needed?

in the above, I mean the req parameter sent to various phase handling 
callbacks.

Q3:  Are there any time-based call backs we can implement through 
mods?  sort of like a rate on a view face.

this would be very usefull:

-it could allow me to keep statistics on mod internals at regular 
intervals ex:  average load, high/low peaks, 

-perform cash cleanup/buildup, ping remote tools for "I am alive" 
monitors, etc.

I hope there is a simple trick I don't see at the moment:

As a result of an RSP script I want to return a new web-page that's 
on the file-system. I do it like this:

print read %payment/index.html


So far this works. What I need to do is, to insert some dynamic content 
into the read HTML file.

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.