World: r3wp

is it just curl? i will try from rebol 1st

from rebol, it's okay...


>> delta-time [read/custom http://localhost:8080/docs/rfq3 reduce 
['post read %xxx] ]
connecting to: localhost
== 0:00:00.034002

it has something to do with the connection keep-alive

curl --http1.0 ... is fast

yes, the http connection will not close until it times out.


if the curl command line waits for ip close to return, its possible 
that is what is happening.

there are probably ways control this via some curl command line options?

i was trying an explicite response/set-header 'connection "close", 
but it didn't help..

see the --http1.0 option above. with that there is no Connection: 
keep-alive  header sent  (or maybe there is, but in HTTP/1.0 mode 
it is ignored)

it shoudn't send it.  the servers are always free to implement more 
headers than the spec.

also realize that if you use http 1.0 there are no virtual hosts!! 
supported so its a bit deal.

bit = big

with the --no-keepalive option, this magic 2seconds delay is still 
there

If you haven't figured out the COLLECT rewrite yet, let me take a 
look.

hmm... does cheyenne handle the Expect: 100-continue header?

i couldn't really find any signs of it. the http-responses mentiones 
the code 100, but that's all, im afraid

Here is a workaround (by raping curl):


$ time curl -H 'Expect:' -d @xxx -D- http://localhost:8080/docs/rfq3
real    0m0.082s

HTTP code 100: not supported, if you have a (not obscure) use-case 
for that, I might add support for it.

Keep-alive: IIRC, Cheyenne doesn't honor the "Connection: close" 
case with HTTP1.1.

BrianH: I've found a workaround for COLLECT (just replacing DO by 
*DO which refers to the native function in RSP environment). Can 
you tell me if there are other recently added mezzs (from R2/Forward 
mainly) that rely on DO in their implemenation?

the module stuff, probably.

I would need to patch them one by one when used in RSP.

(should be a one-line patch like for COLLECT, so not a big deal)

APPLY and MAP-EACH, so far.

Both of them do a block though.

Thanks, will patch them too.

Oh, if it's a block!, then it should work in RSP.

IN-DIR also does a block.

None of need rebinding though, as they get all of their non-locally-bound 
words from the calling context, so it might be worth patching them 
anyways.

Will look into that.

hmm... it was more troublesome to include the R2/Forward as we thought... 
:/

regarding the Expect: 100-continue, i don't have any other realistic 
usecase other than this is the default behaviour of curl...

In APPLY, the QUOTE function is added to the constructed block containing 
the function call. If you don't do something fancy with that function, 
no rebinding is needed. That function should really be protected 
in the runtime though; a *lot* of runtime code absolutely depends 
on these low-level control functions to behave *exactly* as they 
are expected to. Same goes for ALSO.

personally, i never had to use such negotiations which wouldn't accept 
a request..

There are no other functions than those 3 that were added in the 
last 3 versions that call DO explicitly. The rest of the functions 
that call DO explicitly were in 2.7.5, so R2/Forward additions don't 
apply.

4, including COLLECT :)

I'm trying the latest binary version of Cheyenne. I've added fast-rebol-cgi 
to the globals, but the conf-parser log says this is invalid. How 
is this keyword supposed to be used?

show.cgi stays blank. trace.log gives me this, which I wouldn't expect 
in a Linux build:

20/4-04:00:21.407196-[CGI] Error:/bin/bash: c:devsdktoolsrebol.exe: 
command not found

I took the extra files from the 0.9.20 source

Kaj: just change the 1st line of show.cgi to point to the right rebol

we were talking about this 2 days ago w Doc and i even wrote a script 
which finds the right exe and patches the 3 example cgi files

hm... how is the DELETE method supported? im getting 405

mod-static.r 74:		unless find [HEAD GET POST PUT DELETE] req/in/method 
[

doesn't help alone. im getting 404 now :/

we are trying to interface cheyenne with the angularjs.org - fyi

luckily we can set a deleted attribute for now if we really want 
to delete something, but that's just a workaround

fast-rebol-cgi: I guess I forgot to declared it as a config keyword, 
I'll fix that now.

show.cgi: I can't provide a CGI script that would work out of the 
box on all OSes and every possible local configuration, so I've left 
it as-is for users to adapt the shebang line. Using onetom's setup 
script might be the best solution, I'm thinking about integrating 
it in the Cheyenne sources package.

Kaj: fast-rebol-cgi issue fixed in revision 131. If you need a new 
Linux binary, I can build you one (just let me know if you prefer 
a /Pro or /Cmd version).

onetom: DELETE is not supported by default, but it can be easily 
hacked in as you did (note to myself: add a config option to enable 
additional HTTP methods).

No 404 here:
>> p: open/no-wait/direct tcp://localhost:80
>> insert p "DELETE /show.rsp HTTP/1.0^/^/"
>> probe copy p
{HTTP/1.1 200 OK
Server: Cheyenne/0.9.20
Date: Wed, 20 Apr 2011 11:06:16 GMT
Content-Length: 520
Content-Type: text/html
Connection: close
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: -1

<HTML>
<HEAD>
^-<TITLE>RSP Test Page</TITLE>
</HEAD>
...

ok, let me dig deeper then. meanwhile since u r planning a new release, 
can u "enable" the DELETE method too?
the changelog can say: preliminary, dumb, DELETE method "support"
it's still better than nothing

pleeeease :)

I think that the config option is a better way to handle it. I prefer 
returning a 405 error code to online web scanners for the 99% of 
Cheyenne servers that don't need DELETE.