World: r3wp

Across all R projects on Ohloh, 6.1% of all source code lines are 
comments. For cheyenne-server, this figure is only 0.4%. 

how many R projects are on Ohloh??

REBOL is not recognized by Ohloh's parser. It thinks that it's coded 
with R (statistical analysis language), so stats related to code 
are wrong.

Their parser is open-sourced : http://sourceforge.net/apps/trac/ohcount/

Anyone interested in adding REBOL support? (requires knowing/learning 
Ruby)

There are a couple of projects by Volker referenced there .. but 
I didn't see any source code.

Ohloh is crawling in Google Code's and probably Sourceforge's repositories. 
Volker has a few projects in Sourceforge.

There's no REBOL in the drop down list of programming languages :(

You have to sign up, confirm your email, and then confirm your email 
subscriptions before you can add cheyenne-server!

Ok, cheyenne-server is now up to 2 users!

I'm need to get the name I assigned a face when I alt-click on it. 
I can get its style, offset, size etc but I do not see a way to get 
the face's name. More specificly I have multiple scroll-panels and 
I need to know the one I'm clicking in...

Sorry wrong group

I want to be able to use cheyenne's MTA from Rebol.

in email.rsp, modify the lines at 43 to this

	if block? file: param/file [
		file/1: to-file file/1
		if file/2 [
			attempt [
				file/2: to-file file/2
			]
		]

And this works ...


myname: "Graham Chiu"
myemail: [gchiu-:-compkarori-:-com]
toemail: [dontspamme-:-gmail-:-com]
subject: "testing Cheyenne"
msg: "Yes, this i a message"
file: "encap-paths.r"
path-to-file: %/c/chesvn/Cheyenne/encap-paths.r



result: read/custom http://localhost:7900/email.rsp reduce compose/deep 
[ 'POST
	rejoin [
	"from=" (myname)
	"&from=" (myemail)
	"&to=" (toemail)
	"&subject=" (subject)
	"&msg=" (msg)
	"&file=" (file)
	"&file=" (path-to-file)
	]
]

use whatever port your Cheyenne is running on

because I use duplicate cgi names .. ie. from and file, they are 
turned into a block when processed

And this means order is important

instead of 

if file/2 [

can try

if all [ file/2 not empty? file/2 ]

Nice idea! A REST-like interface to Cheyenne's MTA using the demo 
email form. :-)

yeah ... like FormMail.pl ... all spammers invited :)

I like the fact that I can pass a file! so that I don't have to figure 
out how to do a multipart upload to the mail.rsp script.

in email.rsp we have the following ..

	;-- check attach file and format it for send-email
	ten-mega: 10 * (2 ** 20)
	if block? file: param/file [
		file/1: to-file file/1
		

  either file? file/2 [	; check case where uploaded file has been streamed 
  on disk
			if any [not exists? file/2 ten-mega < size? file/2][
				print "Attached file not found or size above 10MB limit!"
				response/end
			]
			file/2: read/binary file/2
		]
		param/file: reduce [param/file]
	]

the either file? is missing the second conditional block .. I presume 
the first block checks to see if file/2 is of file type and the other 
type is binary

I guess change the 'either to an 'if

Also in chrome when you select a file, it just shows the filename 
... I wonder if and where it is storing the full path.

How can I stop the browser from caching the response/buffer ?  I 
set the response butter and content type, but the browser seems to 
be caching the buffer.

set the headers I guess

see the header I set in 'reform-headers here : http://code.google.com/p/cheyenne-server/source/browse/trunk/Cheyenne/mods/mod-action.r#

headers

SVN r30 :


FEAT: MTA engine refactored, jobs are split in sub-tasks allowing 
more reliable and cleaner code.
FEAT: Default SMTP delay reduced to 5mn.

FEAT: MTA queue can now be saved on disk when server is restarted 
(persist [mail-queue])

FEAT: added native DNS async wrapper for UniServe (protocols/DNS.r)

FEAT: replaced blocking DNS calls for MX domain resolution by async 
DNS calls.

FEAT: 'on-mx event in DIG protocol now returns a block of all the 
declared MX.

FEAT: now all MX will be tried in right order by the MTA if connexion 
fails.
FEAT: improved SMTP logs by prefixing with a SMTP session ID.

FEAT: upload data in HTTPd limited to 2GB (max supported by integer! 
type)

FEAT: 'email-info? RSP function return data format improved (see 
email.rsp header)

FIX: email.rsp minor bugs fixed and From: field added.
FIX: minor fixes in email.r library.

FIX: now uni-engine's logging level is also set by 'set-verbose function.

Due to heavy changes in the MTA engine, regressions can happen. All 
my tests are working ok so far.

Btw, you can see a nicely formatted diff of all the changes here 
: http://code.google.com/p/cheyenne-server/source/detail?r=30
(click on [+] to see the changes)

I'm just trying to do a file upload using RSP ... see http://rebol.wik.is/Cheyenne/Upload-file.rsp

What I'm getting however is this


request/content is [file "%/C/Cheyenne/incoming/oixaqcdg.tmp^M^/"]

and the file contains all the post variables and data

If the post data is over a certain size, it gets put in a temporary 
file that you can read.

I assumed it only put file data there and still captured the non 
file data into request/content

It even does it with non-file posts of sufficient size.

oh well ....

You can set the cutoff size in the config file.

I'm going to have to load it back into memory in my rsp script anyway

in httpd.cfg ?

Yes. It's probably to cut down on interprocess communication between 
the host and worker processes. The RSP is processed in a different 
process than the web server process.

do you know what the setting is?

I'd have to look it up. Give me a sec.

data: decode-cgi dehex read/binary %temp.tmp ....

post-mem-limit, in web-app, in bytes.

under globals?

Under web-app (at least that's where I used it).

sorry, webapp

Check both.