AltME groups: search

how long has the latency been running on the mailing list.  I posted 
earlier and my post still didn't show up.

my message reached the list at http://mail.rebol.net/cgi-bin/mail-list.r
but didn't get out again back to me.

from the mail list

Date: Sun, 23 Jan 2005 17:03:16 +0100
From: Bryan Rasmussen <[bry-:-itnisk-:-com]>
Reply-To: [rebolist-:-rebol-:-com]
To: [rebolist-:-rebol-:-com]
Subject: [REBOL] Intro to Rebol article for DevX



Hi, i've been asked to write an intro to rebol article for devX, 
a task for

which there are any number of people better suited and for which 
i wouldn't have

the time anyway. So if anyone is interested in writing this i can 
direct the

devx editors to you as i still follow this list well enough to know 
who knows,
even if i hardly ever use the language anymore. 


-- 
Bryan Rasmussen

right, since your in the group, in the first place... but that leaves 
guest on the list after and is not very nice for truely private groups... 
such a thing can go unnoticed by the group's "manager"

What, are you the Altme nazi?  If you look a bit higher up this list, 
you'll find your own "out of group" messges.

I have a slightly modified help, that does not evaluate functions 
in objects and ports and that also dumps ports like objects.
>> a: open http://www.rebol.com
connecting to: www.rebol.com
>> help a
A is a port of value:
   scheme          word!     HTTP
   host            string!   "www.rebol.com"
   port-id         integer!  80
   user            none!     none
   pass            none!     none
   target          none!     none
   path            none!     none
   proxy           object!   [host port-id user pass type bypass]
   access          none!     none
   allow           none!     none
   buffer-size     none!     none
   limit           none!     none

   handler         object!   [port-flags open-check close-check write-check 
   ini...
   status          word!     file
   size            integer!  0
   date            date!     6-Nov-2006/21:26:44
   url             string!   "http://www.rebol.com/"

   sub-port        port!     make port! [ scheme: 'tcp host: "www.rebol.com" 
   po...
   locals          object!   [list headers querying]

   state           object!   [flags misc tail num with custom index 
   func fpos i...
   timeout         integer!  30
   local-ip        none!     none
   local-service   none!     none
   remote-service  none!     none
   last-remote-service none! none
   direction       none!     none
   key             none!     none
   strength        none!     none
   algorithm       none!     none
   block-chaining  none!     none
   init-vector     none!     none
   padding         none!     none
   async-modes     none!     none
   remote-ip       none!     none
   local-port      none!     none
   remote-port     none!     none
   backlog         none!     none
   device          none!     none
   speed           none!     none
   data-bits       none!     none
   parity          none!     none
   stop-bits       none!     none
   rts-cts         logic!    true
   user-data       none!     none
   awake           none!     none

Is there interest in including in the new release?

known and on the list for next release.

because the ticket was created much after the list for 2.7.6 was 
created :-)

maybe we should follow reichart's bug fixing rules... but i can't 
redo the list ten times...

i don't think there's a fixed list that has been written yet.

Shall I create a R3 list here then ?  :(

R3 list initial release - BrianH, Anton, Volker, Henrik, Ashley, 
Graham, Gregg, Dockimbel, Sunanda, btiffin ... simply ppl who are 
skilled, and/or actively use Rebol with own projects ...

All right.  Two Brians...We win.

But Pekr;  RT has to be careful with this.  Giving it out to too 
many will just generate

too much noise...  I'd gladly take my name off the list and wait, 
as to not overwhelm

those in more appropriate positions...I'd rather get handed Government 
Reject Unfit

for Normal Training work.  Not that it isn't a nice shiny carrot 
dangling ever so close

to the nose.  And, being a little schizoid, I also agree with you.

I surely hope you allow us to nominate you for Secretary of the (proposed) 

REBOL User Group. The (proposed) Executive Summary could definitely 
use your
candor.  :)

then it's probably been forgotten in Gabriele's priority list for 
2.7.6.

(Also, I just copy/pasted without adding Retval to the local variable 
list)

And this gives you easy access to many useful mailing list threads 
-- often containing "worked examples" in answer to specific problems:
http://www.rebol.org/ml-topic-index.r?i=parse

Pekr, I see now this is the same newbie trap you pointed out to me 
over 2 weeks ago. Difference is that this time I understand what 
you mean. (i hope).

I think I need to study backtracking now.  I just discovered this 
discussion that seems very helpfull on the subject.

http://www.mail-archive.com/[list-:-rebol-:-com]/msg03371.html  I wonder 
if I should start using Rebol 3 ?  does it have this enhancement 
yet? is it stable enough for educational use would you say? or is 
is really only the domain of testers as yet?  Thanks.

It's very easy to create prototypes and VID is excellent for that:

view layout [
	across space 2
	box blue 300x300 "List View"
	box yellow 100x300 "Buttons"
	return
	box red 402x24 "OK/Cancel Panel"
]

Large message coming, with examples of showing progress. Note that 
it uses INCLUDE and FILE-LIST, so adapt accordingly, and let me know 
if I left any other dependencies in it that cause it not to work. 
It was quickly hacked from existing code.

REBOL []

do %include.r
include %file-list.r


flash-wnd: flash "Finding test files..."

if file: request-file/only [
    files: read first split-path file
]
if none? file [halt]

items: collect/only item [
    foreach file files [item: reduce [file none]]
]

unview/only flash-wnd



;-------------------------------------------------------------------------------
;-- Generic functions

call*: func [cmd] [
    either find first :call /show [call/show cmd] [call cmd]
]

change-each: func [
    [throw]

    "Change each value in the series by applying a function to it"

    'word   [word!] "Word or block of words to set each time (will be 
    local)"
    series  [series!] "The series to traverse"

    body    [block!] "Block to evaluate. Return value to change current 
    item to."
    /local do-body
][
    do-body: func reduce [[throw] word] body
    forall series [change/only series do-body series/1]

    ; The newer FORALL doesn't return the series at the tail like the 
    old one

    ; did, but it will return the result of the block, which is CHANGE's 
    result,
    ; so we need to explicitly return the series here.
    series
]

collect: func [
    "Collects block evaluations." [throw]
    'word
    block [block!] "Block to evaluate."
    /into dest [block!] "Where to append results"
    /only "Insert series results as series"

    /local fn code marker at-marker? marker* mark replace-marker rules
][
    block: copy/deep block
    dest: any [dest make block! []]

    fn: func [val] compose [(pick [insert insert/only] not only) tail 
    dest get/any 'val

        get/any 'val
    ]
    code: 'fn
    marker: to set-word! word
    at-marker?: does [mark/1 = marker]
    replace-marker: does [change/part mark code 1]
    marker*: [mark: set-word! (if at-marker? [replace-marker])]
    parse block rules: [any [marker* | into rules | skip]]
    do block
    head :dest
]

edit-file: func [file] [
    ;print mold file

    call* join "notepad.exe " to-local-file file ;join test-file-dir 
    file
]

flatten: func [block [any-block!]][
    parse block [

        any [block: any-block! (change/part block first block 1) :block | 
        skip]
    ]
    head block
]

logic-to-words: func [block] [

    change-each val block [either logic? val [to word! form val] [:val]]
]

standardize: func [

    "Make sure a block contains standard key-value pairs, using a template 
    block"
    block    [block!] "Block to standardize"
    template [block!] "Key value template pairs"
][
    foreach [key val] template [
        if not found? find/skip block key 2 [
            repend block [key val]
        ]
    ]
]

tally: func [

    "Counts values in the series; returns a block of [value count] sub-blocks."
    series [series!]
    /local result blk
][
    result: make block! length? unique series

    foreach value unique series [repend result [value reduce [value 0]]]
    foreach value series [
        blk: first next find/skip result value 2
        blk/2: blk/2 + 1
    ]
    extract next result 2
]


;-------------------------------------------------------------------------------

counts: none

refresh: has [i] [
    reset-counts
    i: 0
    foreach item items [
        i: i + 1
        set-status reform ["Testing" mold item/1]
        item/2: random/only reduce [true false]
        show main-lst
        set-face f-prog i / length? items
        wait .25
    ]
    update-counts
    set-status mold counts
]

reset-counts: does [counts: copy [total 0 passed 0 failed 0]]

set-status: func [value] [set-face status form value]

update-counts: has [pass-fail] [
    counts/total: length? items

    pass-fail: logic-to-words flatten tally collect res [foreach item 
    items [res: item/2]]
    ;result (e.g.): [true 2012 false 232]
    standardize pass-fail [true 0 false 0]
    counts/passed: pass-fail/true
    counts/failed: pass-fail/false
]

;---------------------------------------------------------------


main-lst: sld: ; The list and slider faces
c-1:           ; A face we use for some sizing calculations
    none
ml-cnt:        ; Used to track the result list slider value.
visible-rows:  ; How many result items are visible at one time.
    0

lay: layout [
    origin 5x5
    space 1x0
    across

    style col-hdr text 100 center black mint - 20

    text 600 navy bold {

        This is a sample using file-list and updating progress as files are
        processed. 
    }
    return
    pad 0x10

    col-hdr "Result"  col-hdr 400 "File" col-hdr 100
    return
    pad -2x0

    ; The first block for a LIST specifies the sub-layout of a "row",

    ; which can be any valid layout, not just a simple "line" of data.

    ; The SUPPLY block for a list is the code that gets called to display

    ; data, in this case as the list is scrolled. Here COUNT tells us

    ; which ~visible~ row data is being requested for. We add that to 
    the

    ; offset (ML-CNT) set as the slider is moved. INDEX tells us which
    ; ~face~ in the sub-layout the data is going to.

    ; COUNT is defined in the list style itself, as a local variable 
    in
    ; the 'pane function.
    main-lst: list 607x300 [
        across space 1x0 origin 0x0
        style cell text 100x20 black mint + 25 center middle
        c-1: cell  cell 400 left   cell [edit-file item/1]
    ] supply [
        count: count + ml-cnt
        item: pick items count
        face/text: either item [
            switch index [
                1 [

                    face/color: switch item/2 reduce [none [gray] false [red] true [green]]
                    item/2
                ]
                2 [mold item/1]
                3 ["Edit"]
            ]
        ] [none]
    ]

    sld: scroller 16x298 [ ; use SLIDER for older versions of View

        if ml-cnt <> (val: to-integer value * subtract length? items visible-rows) 
        [
            ml-cnt: val
            show main-lst
        ]
    ]
    return
    pad 0x20
    f-prog: progress 600x16
    return
    status: text 500 return
    button 200 "Run" [refresh  show lay]
    pad 200
    button "Quit" #"^q" [quit]
]

visible-rows: to integer! (main-lst/size/y / c-1/size/y)

either visible-rows >= length? items [
    sld/step: 0
    sld/redrag 1
][
    sld/step: 1 / ((length? items) - visible-rows)
    sld/redrag (max 1 visible-rows) / length? items
]

view lay

hehe, Tom Halwerda got reply from someone from Syllable team apparently 
:-)
-------------------

 By Vanders (IP: ---.cable.ubr02.chap.blueyonder.co.uk) - Posted on 
 2005-07-04 22:34:20
Sorry Thom but you're wide of the mark on several counts.


Systems like the Amiga or BeOS failed for a number of reasons, but 
mostly because they were either tied to a minority hardware platform 
and through sheer poor management. It's fair to say that both were 
ahead of their time, which was certainly a contributing factor. We'll 
add NeXT to this list while we're here. Syllable and SkyOS are written 
for generic Intel PC hardware, and neither are old enough to know 
if Robert or I will kill either through bad management!


Sure we want to compete with Linux. Linux is a great OS on the server, 
it's a sucky desktop. I've been running it for over six years on 
my home PC and several years now in various real-world deployments 
in a server capacity. Year after year, Linux continues to dissapoint 
me as a desktop OS. Why shouldn't we compete with that? Saying "You 
can't compete with Linux!" is just deafeatism. The thing is, Syllable 
is not out to beat Linux. We want to co-exist with Linux and in doing 
so, enhance the Open Source ecosystem. Linux can run the servers, 
Syllable can run the clients. Makes sense to me.


Look, if in two years time us Syllable developers have nothing to 
show for it but an OS that only us six run and are happy with, well 
then that's fine with me! I'm sure as hell not going to roll over 
and pretend that I like using Linux on my desktop though. Why shouldn't 
we try to improve it? Because we might fail? Piffle.

Some quick points to finish off:


o Robert is a good developer but I don't believe he has the time 
or the hardware to have written every single driver for SkyOS from 
scratch. The video drivers are from X & if you asked him, I'd expect 
the NIC & audio drivers are BSDL.

o The Open Source nature of Syllable has never been in impedement 
to implementing features. We have a set or core developers and we 
make the decisions. We have a roadmap and we're following it. To 
paint Syllable as a band of wishy-washy Open Source developers with 
no direction who are somehow bogged down with arguments is misleading 
and dishonest. Just like SkyOS, if we decide a feature must go in 
it goes in.

o I'm not aware of a single company currently working with SkyOS. 
We can sign up for the exact same Developer Relations schemes as 
Robert can. Many companies don't seem to mind that Linux is Open 
Source, I fail to see how Syllable is any less legitimate in this 
regard.


Hard is the whole point Thom! What's the point in doing easy? Anyone 
can do easy!

5 Core developers, maybe 50 that have contributed at some time, 500 
on the mailing list, more than 1000 on the forum, 5000 who download 
each install CD, more than 10,000 who download each live CD and emulator 
image, tens of thousands who come visit when we're on OSNews, roughly 
an order of magnitude more when we're on Slashdot

Since the publication, Apple has already come to our mailing list 
to ask us to join their WebKit project

I'll put it on my list to look into. I think it would qualify as 
an operating system grade extension

What console is he running?  Under Konsole the list of encodings 
is overwhelming.  (From the Settings menu).

If it's xterm, then ... I dunno, but regardless, if it is xterm or 
other, drop a note and we'll track down an appropriate place to tweak 
the default encoding used by his REBOL console (whatever terminal 
he uses) session.


It might be easier (some gui menu), but it could well look something 
like

XTerm*locale: true

XTerm*font:             -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

in an X config file


From the root text console for REBOL/Core, we'd have to look into 
that as well; been there, kinda done that, too many details, forget 
all details, but keep foggy clue where to start looking ...  :)

someone on french forum reports that the ctrl key doesn't allow to 
select text in text-list like it does in the windows version

Yes, text-list is very underpowered.

Ah wait. No, I can ctrl-click text-list here on Kubuntu 7.10.

view layout [text-list data ["hello" "bonjour"]]

And, is there a list of required libX... ?

And, is there a list of required libX... ?

Does REBOL work with Suse Linux? I can see Debian in the list, so 
I expect it to work with Ubuntu for e.g.?

I think there is a list of needed lib files that some distros may 
not include in the basic install. I assume they can be added....

ldd    will list dependencies for any object or binary.
Tracking which package (as Robert mentions can be a pain, but)

after  apt-get install apt-file   and  apt-file update   it gets 
easier.

Gobo, Unbuntu, Debian

So far three...


I'm going to put together a list of applcation I run regularly, and 
then we can weigh this again...

I now seem to be able to list windows associated with a given process 
id. I've tried the konsole pid, and I get five result windows...

OK, got it working on Ubuntu (and Mac) with:

fonts: copy []

foreach [font-name style] parse/all (call/output "fc-list" s: copy 
"" s) ":^/" [
	all [
		not find fonts font-name

  (size-text make face [text: "A" font: make face/font [name: font-name 
  size: 10]]) <>

  size-text make face [text: "A" font: make face/font [name: font-name 
  size: 12 style: 'bold]]
		insert tail fonts font-name
	]
]
sort fonts

console-port: open/binary/no-wait console:/
console-port/awake: func [port /local ch][
	if ch: pick port 1 [
		;print ["Console awake trapped key:" to-char ch "(" ch ")"]
		either ch = #"^V" [	; Ctrl+V

   call "xclip -o -selection clipboard" ; Three different types of clipboards: 
   "primary", "secondary" or "clipboard".
		][
			insert system/ports/output to-char ch
		]
	]
	return false ; Does not cause return from WAIT (DO-EVENTS).
	;true ; Does cause return from WAIT (DO-EVENTS).
]

insert system/ports/wait-list console-port
if error? set/any 'err try [
	do-events
][
	print mold disarm err
]
close console-port
remove find system/ports/wait-list console-port

setup file is like this: 
#!/bin/bash
#
# iptables example configuration script 
#
# Let's not lock ourselves out of the server
#
 iptables -P INPUT ACCEPT
#
# Flush all current rules from iptables
#
 iptables -F
#
# Allow SSH connections on tcp port 22

# This is essential when working on remote servers via SSH to prevent 
locking yourself out of the system
#
 iptables -A INPUT -p tcp --dport 22 -j ACCEPT
#
# Allow HTTP connections on tcp port 80
#
 iptables -A INPUT -p tcp --dport 80 -j ACCEPT
 iptables -A INPUT -p tcp --dport 443 -j ACCEPT
#
# Set default policies for INPUT, FORWARD and OUTPUT chains
#
 iptables -P INPUT DROP
 iptables -P FORWARD DROP
 iptables -P OUTPUT ACCEPT
#
# Set access for localhost
#
 iptables -A INPUT -i lo -j ACCEPT
#
# Accept packets belonging to established and related connections
#
 iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
#
# Save settings
#
 /sbin/service iptables save
#
# List rules
#
 iptables -L -v

When using LD directly, how can I specify that the default libs are 
inlcuded without having to list them all?

might be missing a library file...check the list of required libs...find 
it somewhere on rebol site???

If I run a simple REBOL script (with just a forever loop), I notice 
that "ps -a" gives me two REBOL processes in the process list. Why 
is this?

Use this to determine which [scaleable] fonts are available:

			fonts: copy []
			call/output "fc-list" s: copy ""
			s: parse/all s ":^/"
			foreach [fn style] s [
				all [
					not find fonts fn

     (size-text make face [text: "A" font: make font [name: fn size: 10]]) 
     <>

     size-text make face [text: "A" font: make font [name: fn size: 12 
     style: 'bold]]
					insert tail fonts fn
				]
			]

Before mucking with a recursive chown, I would recursively list your 
files and save into a file, eg:
$ ls -lR > listedfiles
(that first option is a lowercase L ).

Then later if you are worried about having blasted some particular 
permissions, you just refer to listedfiles.

max, you can add those to your dependency list

<If I only was a bit sure that there would be enoough compatibility 
between R2 and R3...>

They will be highly compatible, but with enough changes to break 
many scripts. As far as I know there is no definitive list of confirmed 
incompatibilities on the R3 wiki. A quick scan of the R3 blog offers 
some clues:
http://www.rebol.net/cgi-bin/r3blog.r?index=0

I think NickA has also posted some scanning stuff on the mailing 
list, or on his website.

in R2:

map: func [vars list exec /local res][res: copy [] do reduce [:foreach 
vars list compose [append res (exec)]] res]
>> map [a b][1 2 3 4][a * b]
== [2 12]
>> map [a][1 2 3 4][a * a]
== [1 4 9 16]

and if you always use the same vars (like x, y and z) you can simplify:

 map: func [list exec /local res][res: copy [] do reduce [:foreach 
 intersect [x y z] exec list compose [append res (exec)]] res]
>> map [1 2 3 4][x * x]
== [1 4 9 16]
>> map [1 2 3 4][x * y]
== [2 12]

In your first version, you have a problem if the vars list includes 
the vars 'append or 'res. You need to compose your loop differently.

map: func [vars list exec /local res][res: copy [] do reduce [:foreach 
vars list compose [append (res) (exec)]] res]
is that ok now ?

map: func [vars list exec /local res][res: copy [] do reduce [:foreach 
vars list compose [(:append) (res) (exec)]] res]

simpler:

map: func [vars list exec][do reduce [:foreach vars list reduce [:append 
[] :do exec]]]

and finaly, we can use a single var:

map: func ['vars list exec][do reduce [:foreach to-block vars list 
reduce [:append [] :do exec]]]

>> map [x][1 2 3 4][x * x]
== [1 4 9 16]
>> map x [1 2 3 4][x * x]
== [1 4 9 16]

For that matter, the to-block is also unnecessary. Try this:

map: func ['vars list exec][foreach :vars list reduce [:append [] 
to-paren exec]]

Each of those functions I am referring to has their own parameter 
list.

and I used a simple face timer to poll through the async contexts 
to see if the xfer was finished.  then call the on-close event. and 
remove it from the list of "pending" xfers.

the checkup loop was something like


you can do it that way too... but you might get into some strange 
stack issues, cause you end up handling  port messages from one port 
to another within the messaging stack... but I guess a simple test 
sould suffice to see if its stable or not.


in my case, the gui had to stay responsive, since the xfer-contexts 
had cancel methods, which interrupted any xfer in real-time, and 
the whole gui had to still handle events smoothly, like scrolling 
a huge list, while it was adding items to that list, as it parsed 
the return value from the google search engine  :-)

and to set individual "done" bits

xfer-context: [
  set-done: does[ 
     done-bits: done-bits OR power 2 index? find port-list self
  ]
]

:-)

Well, if you assume that your internal storage method is one which 
just needs to be "converted" to an other, like CSV => XML, you might 
be in for a suprise when trying to model a real time dynamic system 
with Undo like a paint program with a file format as export.


For example, do you store a given object once, with the history of 
the object elsewhere, or do you store the object together, with the 
most recent at the top of the list.

Also, Do you store objects, and actions, or both togther.

toggle ar too big in my opinion a toggle is to be put in a list of 
parameters

To get list of operators:

>> ? op!

it is normal that hash! will only hash "keys" of assoc on first level, 
if you want on sublevels you can iterate the list and turn it into 
hashes acordingly .. if you have a lot of data hash is a lot faster 
650x in this test http://www.rebol.com/article/0020.html

With RebGUI state, although VID my be more free-form, I refuse to 
even touch the thing, which does not have scrollers with area, list-box 
is not indexed and it hilites two the same values, and tonnes of 
other problems ...

I'm sure I don't want VID improvements before of rebcode.... I want 
CORE with rebcode first... And I really hope that some release  will 
not be postponed just because there is no  new tree-list GUI or something 
else

List of printers supporting Level 2 PostScript directly without software 
driver as of 2/2/1998:
http://www.postscript.org/FAQs/language/node95.html

AddHandler: it's on my Todo list for 1.0 :-)

In the meantime, I have also on my todo list a dedicated web site 
for Cheyenne. I'll work on that in the next days.

It's not on my Todo list, I plan to make a higher level framework 
for building web applications, where I don't want to mess anymore 
with HTML or Javascript. Kind of VID dialect that compiles to HTML+CSS+JS.

extension-class: context list

and replace it with :

extension-class: context to-block list

just extend the method block list with whatever method you need

The last one in the list will be the last loaded, so will be able 
to take the FIRST or LAST place even if other previously loaded mods 
did the same.

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
    ]
]
>>

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 [ ]

BrianH: do you have a list of patches to apply to R2.7.6 ?

Byte-Ranges

 -- way down the roadmap list after big-sounding items :-()  I have 
 to wait. No problem.

I'm having trouble getting Cheyenne running as a service with windows 
server 2003. I get this message when I try to start from the services 
list:
	Could not start Cheyenne Web Server service on local Computer.

 Error 1053: This service did not respond to the start or control 
 request in a timly fashion.

SID & session/start : I've added that to my todo list, need to think 
about that deeper before implementing.

Graham: you can set your webapp (or at domain level) in debug mode 
(using the 'debug keyword in config file). If the debug mode could 
be tested, it could allow you to enable/disable the captcha system 
(or anything else) based on the working mode (debug / in production). 
I'll add that to the todo list also.

Well, I think that I should make the timings optional. I'll add that 
to the to-do list, thanks.

:-) Anyway I'll add BA on my todo list.

Max, that would require writing a specific module for Cheyenne. Connections 
number can be measured by doing a : length? system/ports/wait-list 
(and subtracting worker processes local connections).

Max, not sure that it can help you, but you can open a live REBOL 
console connected to a running Cheyenne instance (only from localhost). 
You can then use the NETSTAT function to list all active connections 
in realtime. The client for connecting is : %UniServe/clients/rconsole.r

About your feature request, I understand that your "on-allow-connection?" 
event would be generated just after the connection between the client 
and server is established? If it's the case, then you already have 
the "on-new-client" callback where you can decide to reject the connection 
or send back an error message if required (I often use it to reject 
connection based on IP adress access list).

Btw, you can run Cheyenne in verbose mode (-vvv or even -vvvvv), 
it's easier to debug this way. During the boot process, Cheyenne 
will list mods callback matrix allowing you to see/debug the execution 
order for your mod's callbacks.

There's maybe some info about that flying around in the mailing list 
archives from RT staff (Holger or Jeff probably).

There's no way to have the debug mode without the debug menu currently, 
but it should be easy to add an option to define the debug level. 
I'm adding that to v0.9.20 todo list (scheduled for releasing before 
the end of this month).

Graham: I'm putting this issue higher in my todo list, shouldn't 
require much work to make it fully multi-instance safe.

I make a hash! list of all the phases' callbacks, so the impact on 
performances remains very low.

Re: JS warning in Firebug : that's intentional, it's not a bug, but 
it is bad practice. I'm putting that in my todo list.

Sounds useful, adding your RFE to my todo list.

Anyway, I'll try to list and add one or two comment lines for each 
available option in the next release, but I won't spend days writing 
docs for the config file.

as a point of fact, it is very possible that some modules (like remark) 
will require stuff to be setup which is hard to simulate through 
a gui.  managing a system of nested parameters and list is very complex 
to handle programatically.

True about the tunneling tools, but I'm not the server guy so I don't 
know why they are still using Apache for the main site. I know they 
aren't married to it since the site isn't built on unique Apache 
modules, and because they mention looking at other servers. It wouuld 
depend on performance and scalability, so an alternate soltion would 
need to outperform and outscale Apache and FastCGI. As for the RSP 
features Maarten is adding, don't know what they are yet - it's on 
my todo list to compare the two RSPs to determine if there are features 
that the other could use.

Well, there's just a local dependency on config file to remove first 
(in my todo list) to allow remote worker process (for RSP, CGI,...). 
But you need a also a remote process manager to handle the launching 
of worker processes. Anyway, I think that using a front load balancer 
(supporting session affinity) with several servers is a simple and 
efficient solution.

Word capturing => yes, all RSP running inside a webapp are captured 
in the webapp execution context, to avoid global context pollution. 
This doesn't apply to standalone RSP scripts (outside a webapp), 
but that feature could be easily added.


Page inclusion => yes, you can include RSP scripts in RSP. See http://cheyenne-server.org/docs/rsp-api.html#def-21

context injection with 

captured" words on the subpage" => I don't understand precisely what 
you describe here. In Cheyenne/RSP, subpages are captured in the 
webapp unique context, like parent pages, so there's no special treatment 
for subpages. Do you imply exporting just a selected list of words 
from the subpage script to the parent context?

No, but it's in my todo-list for the next release (0.9.20).

I'm seeing some odd root kit like behaviours ... cheyenne is clearly 
serving up pages,, but the icon is gone from the system tray and 
it does not appear in the processes list in the windows task manager!

This looks like it's working in service mode. In Task Manager, be 
sure to list processes from all users (including services).