World: r3wp

What happens when I upload a 300mb file to Cheyenne (hypothetically?)

Currently, you'd better have a lot of RAM ;-). File upload support 
is still quite primitive, I'll improved that for the v1.

I am thinking of an S3 scenario where I want to "pipe" a huge file 
upload to Amazon S3 (as example)

You'll need something like a mod-proxy (to be implemented) to stream 
your upload to another server.

Yes, but you'd want it to be blocking for the end user in this case 
so he sees the completed status. Question is: will that block Cheyenne?

I already have the HTTP protocol with streaming support for UniServe, 
so this shouldn't be a big work to implement such module (would just 
require to think about how to make it as generic as possible).

With UniServe's async HTTP protocol, it won't block Cheyenne.

Blocking for the end user : sure as long as he hasn't upload all 
the file, he won't receive a response from Cheyenne (that's the HTTP 
protocol).

I see, so the question really is streaming (and proxying the data). 
That 1.0 is gonna be feature-packed ;-)

I'm sure you'll put 1.0 on good stress-tests ;-)

All ;-) aside, any timelines for 1.0 + docs?

Cheyenne should be feature-completed for 1.0 by the end of the month 
(was delayed by other sub-projects, like CureCode). Docs would need 
at least a couple more weeks to be done, so mid-july seems reachable 
for an official 1.0.

Starting from 1st july, I'll be full time on Cheyenne.

cool

Doc,  Will you add a project to CureCode for Cheyenne or do you prefer 
them here?  (he says as though he found one)

I'll add Cheyenne and my other projects (MySQL driver, ...) within 
CureCode once I fix all these annoying little bugs we've found yesterday. 
So I'll wait til the next CureCode release, which should happen by 
the end of this week.

In the meantime, you can report bugs here (only the most important), 
keep the rest for CureCode ;-)

Cheyenne release v0.9.15 beta. Download at http://softinnov.org/tmp/cheyenne-r0915.zip

Changelog :

v0.9.15 - 20/06/2007


 o RConsole was not started by default in the previous release. Fixed
	

 o RSP: 'include function protection from infinite cycles changed. 
 It's

   now based on a counter (5 maximum recursive includes). It's a little 
   less

   cleaner than stack-based tracking but much more reliable (avoids 
   matching
	  paths and targets).
	  

 o HTML.r library rewritten from scratch. Now, faster and more conforming 
 to 

   standards (Full range of Latin1 entities supported). Fixes URL-encode 
   bugs.

	o BugFix for command line parsing in encapped Cheyenne on Linux.
	

 o Fixed an issue with 'decode-multipart in RSP.r. File upload should 
 work ok 
	  again.
	  

 o Added a new global function : 'rsp-log value. Outputs values in 
 console for 
	  debugging RSP scripts. Works as 'probe.
	  

 o Reloading config file now supported. Running sessions and client 
 connections

   survive to the reloading process (needs some additional testing). 
   Activating
	  config file reload is done using:
	  
	  		- (Windows) "Reload Config" menu option in systray icon.
	  		- (UNIX)     kill -s HUP pid
	  		

 o UNIX signals SIGINT,SIGQUIT,SIGTERM now catched to allow cleaner 
 exit and last

   minute actions. Triggers the new 'on-quit event for HTTPd modules.
	

 o HTTPd internal events (not phases) refactored to be cleaner. New 
 module's
	  events added:
	
			- 'on-started:	when Cheyenne starts.
			- 'on-reload:   before a config file reload happens.
			- 'on-reloaded: after a config file reload happens.
			- 'on-quit:     when Cheyenne is about to stop and quit.
			

 o RSP sessions can now be made persistent (can survive to a server 
 complete restart).

   This option is controlled by a new config keyword: 'persist. Usage 
   is :
	  	
	        persist [sessions]    ; other flags can be added at will
	        

 o BugFix in session cookie handling for web-apps using 'auth mode. 
 Now the cookie

   is sent on the 302 redirection to the login page avoiding the creation 
   of a 
	  "shadow session" that will never be used. 
	  

 o FastCGI is under heavy work so mod-fastcgi is commented in config 
 file to avoid

   fastcgi startup. If you want to play with PHP, just uncomment the 
   line.

Go Doc Go!

I'm feeling like running in a marathon ;-)

Tour de France

on steroids?

This is not really about Cheyenne .. but what is the better approach. 
 Using RSP to completely build your page and display it from your 
datasources, or to dynamically construct the page with javascript 
and then feed the data in Ajax like ?

I'm thinking that maybe I should be using RSP to create javascript 
pages that fetch the data using async http ...

my best approach is generate html page as much as you can then load 
dynamic stuff with ajax/js.. you need content for SEO so pulling 
everything with ajax isn't the best approach

..and don't listen to Terry ;-) go with jQuery!

I don't really need SEO because it's a private portal ...

But that is the approach I am tending towards

though it is much easier to just build the entire page in rsp

This is one area QM has sought to resolve.  It's likely it can be 
done with Cheyenne app methods?  Use Hijax -- build an RSP hierarchy:

<template>
  <portion />
</template>


Access %template.rsp when requesting a full page, and %portion.rsp 
when you only want inline content.  Use JS to hijack links to full 
pages and replace them with methods to access and display inline 
content.

.

I have this odd problem with trying to execute a batch script from 
an rsp page.

I do a call/wait and get a return value of 0, but the script doesn't 
actually do what it's supposed to do .. viz. convert a ps file to 
pdf.
but the same batch file called from a rebol console does work.

I don't see why 'call wouldn't work in RSP.

It's very odd...

I put an echo now > when.txt in the .cmd file and it definitely is 
being executed

and returning a 0, even though it doesn't do what it is supposed 
to do ie. invoke ps2pdf

but the same .cmd file works fine in a rebol console.

How about path and other env vars?

paths are all setup correctly

otherwise the cmd file would not work :)

graham, permissions problem?

I wondered about that.  But then it should hang and popup a security 
requester and it doesn't

and since it executes the batch file .. it can't be that.

would it still pop up the sequrity requester if the permissions problem 
is inside the batch file?

how can that happen?

if the batch file calls something of higher privileges. I don't know 
how it works though.

I tried using secure none in the rsp script

made no difference and no requesters came up

I think I have the answer.

I start cheyenne up as a batch file using firedaemon, which turns 
this batch file into a windows service.