World: r3wp

oops ...

>> do %cheyenne.r
Script: "Cheyenne Web Server" (19-Feb-2008)
** Script Error: NT-service? has no value
** Where: boot

** Near: if all [NT-service? not flag? 'service] [set-flag 'tray-only]
>>

Did you applied some TCP networking tweaks on your Vista box to improve 
network latency?

nope

REBOL/View 2.7.6.3.1 14-Mar-2008
Copyright 2000-2008 REBOL Technologies.  All rights reserved.
REBOL is a trademark of REBOL Technologies. WWW.REBOL.COM
>> do %cheyenne.r
make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'context
    arg2: 'blk
    arg3: [block!]
    near: [extension-class: context list]
    where: func [/local list][
        list: extract phases 2
        forall list [change list to-set-word list/1]
        repend list [to-set-word 'service none]
        extension-class: context list
    ]
]
>>

Yes, old bug of 0.9.18 with REBOL 2.7.6.

Doc, do you have a time planned for the public release of 0.9.19?

Either use an older REBOL core or apply the following patch to Cheyenne 
: http://www.digicamsoft.com/cgi-bin/rebelBB.cgi?thread=<9May2008113928682359200>

BrianH: I should have released it a month ago, but some issues with 
RSP showed up and I like to fix them before releasing officially 
the new version.

I ['d] like...

Basically, some errors are not reported or (not catched?) during 
RSP execution. I want to clean up the RSP logging code to output 
all errors to a log file.

with no changes, Cheyenne no longer shuts down using the source version

using 2.6.2

Does that help?

Well, it seems to show that something changed between 2.6.2 and 2.7.6. 
I'm writing a short test server to see if it can be reproduced with 
a short block of code.

what is the current version of cheyenne encapped with?

2.7.6 ?

2.7.5

Ok, try this : paste the following code in a fresh console (2.7.6) 
and try to reproduce the error :

s: open/binary/direct/no-wait tcp://:8003
append system/ports/wait-list s
s/async-modes: 'accept
s/awake: func [server-port /local err new][
	either error? err: try [
		new: first server-port 
	][
		err: disarm err
		if err/code <> 517 [?? err]
		false
	][
		insert tail system/ports/wait-list new
		new/async-modes: [read]
		new/awake: func [port][
			print "event received"
			probe copy port
			false
		]
		set-modes new [no-delay: on]
		false
	]
]
set-modes s [no-delay: on]
wait [ ]

Test with : p: open/direct tcp://127.0.0.1:8003 close p

goes into an endless loop

Does Cheyenne use the EXTRACT function? A bug with EXTRACT with binaries 
slipped into 2.7.6. DevBase has a fix.

event received
none
event received
none
event received
none
event received
none
event received
none
event received
none
event received
none
event received
none
event received
none
event received

BrianH: yes, that's related to EXTRACT but not with binaries, it's 
a side effect of EXTRACT with hash! values.

Graham: does the test line output an error?

no

mmm...if it's really related to some precise timing, it will be hard 
to track.

>> wait [ ]
** Script Error: Invalid argument: true
** Near: set-modes new [no-delay: on]
false

just tried it again

Ok, so we can now fill a nice RAMBO ticket, with an example code 
:-)

Only Vista?

It seems so. Never saw that on XP.

correction, only Graham's laptop running Vista?

Well, you can even send your laptop to Carl if that helps him fix 
that :-)

haha

so, this doesn't go into curecode ?

or is Rambo being kept for R2 stuff

Nope, R2=>RAMBO, as far as I know.

If you run into any mezzanine bugs in 2.7.6+, please bug me about 
them too, I'll fix them :)

Anyway, I'll remove the 'no-delay mode from Cheyenne in 0.9.19 when 
running on Windows.

Don't suppose anyone else is running Vista who can test this too 
...

What is the no-delay mode?

I'd like to keep my laptop here.

No-delay mode: control of the Nagle algorithm in TCP layer.

It's documented here : http://www.rebol.com/docs/core25.html#sect1.2.3.

That sounds interesting. I look forward to reading the source for 
that :)

(in Cheyenne I mean)

so, no-delay = true, nagle is operational?

That would be no-delay = false.

I'll say the opposite.

Right, no-delay = false => nagle in use