World: r3wp

but - you surely know what you are talking about, so I have to be 
wrong :-)

WAIT has many different behaviours depending on the passed argument.

When called with [ ] or [ integer! ], WAIT will process all ports 
stored in system/ports/wait-list. In that case, WAIT will block until 
:

- a timeout is specified and no more events are received for that 
timeout period
- an event returns a TRUE value.

Not sure about the WAIT [port1 port2 ...] case. I guess that it will 
process all events from system/ports/wait-list but will exit on first 
event received by port1, port2,...

just tried to add this before cheyenne starts:
do-events: does [
	forever [wait [0:0:1] print now/time/precise]
]
And from second console run:
loop 1000 [read http://localhost]


the result is, that it prints the time in every second while it serves 
the requests.

In the same time it was serving MP3 from modified micro-http service 
using something like:
    on-received: func [data][
		write-client rejoin[
			{ICY 200 OK} crlf
			{icy-name: LocalRadio} crlf
			{icy-genre: whatever} crlf
			{icy-url: http://127.0.0.1:811} crlf
			{content-type: audio/mpeg} crlf
			{icy-pub: 1} crlf
			{icy-br: 128} crlf 
			crlf
		]
		write-client path-to-mp3-file
	        close-client
    ]

And running my RebolBB with responses <16ms

So Doc was wrong, it's unusual...

Oldes: thanks for taking the time to test it. The correct behaviour 
of WAIT is the one you've described. I'm glad you've corrected me 
on that one. I'm pretty sure that I've run such tests with different 
results when working on UniServe five years ago. Maybe something 
changed in REBOL kernel since then or maybe my test script was just 
flawed. Nice to see that there's still something to learn from R2.

wow, audio streaming in rebol and uniserve .. cool

I need to learn more about thay!

thay -> that

on-write is dissabled in the recent versions. Why?

What makes you think that?

; --- temporary deactivated
			;on-write port

0.9.17	21/12/2004 {
			o Added 'on-write-done event.
			o 'on-write call in 'write-peer temporaly deactivated.
			o bugfix in 'open-port, custom port-id now correctly used.
		}

Right, that was a workaround for a packet sending issue, but never 
had to reactivate it.

It was useful on client side to kickstart first packet sent to a 
server (kind of fast shortcut to avoid a round in event loop before 
sending the first packet), but I had more issues than benefits from 
it, so I left the code deactivated in case I would need it in future, 
but it looks like I could remove those lines. Do you have a need 
for it?

Btw, 'on-write is not disabled in UniServe, it's just no more directly 
called in that specific case.

probably no..  just found it as you told me, that I should control 
the data from it.

Right, controling bandwidth requires changing UniServe's internals, 
mostly in 'on-write handler.

The balloon goes up! I want to move Rugby's transport layer to Uniserve, 
or even better, Cheyenne. (http tunneling). For this to really work 
I only need to know if you have primitives for timers in the event 
loop (inside the 'wait): do-every time! [ code ]  do-after time! 
[code]

The rest will be porting transport and state machines on the server, 
but as Rugby already had a CGI interface it hould be simle to use 
the server with Cheyenne.

That feature is waiting for weeks to be implemented (need it for 
adding a mail relay agent to Cheyenne and for cron-like jobs scheduling), 
I'll give it some time this weekend.

Is this convergence ?  :)

No, this will be world domination ;-)

Rugby to the rescue! I always wanted general multiplexing architecture 
being part of REBOL natively, but then I also wanted simplicity of 
Rugby. Now I will get both? :-)

Maarten - what about Chord concept, is it still valid? Or is there 
anything better out there worth implementing?

btw - what is missing in R3 to start porting of Uniserve to R3? Higher 
level protocols? Or tasks?

Stability maybe? ;-)

First ugby on Uniserve. Then Chord on top of that.... Chord on Rugby 
is already working.

Nenad, this may help you: http://www.colellachiara.com/soft/Libs/timers.r

Chord.. is this that discributted hash table or something else?

yes

hm.. interesting.. is there any more info about it on web somewher? 
( btw: I remember I played with Rugby 8-10 years ago when I was allround 
programming newbie, it looked like total magic to me)

aha, I found this http://www.colellachiara.com/soft/Libs/chord.r

Yes, but that's not working - someting with async ports. I have something 
on top of Rugby that works, but it's too slow.

Has anyone written a IRC server in Uniserve?

( this group is not supposed to be private - made public )

I was looking at uniserve today .. really nicely made .. especially 
if you know that uniserve is running cheyenne which runs so fast 
and well .. I will port my distibuted actors library to use uniserve

What is distributed actors library? sounds interesting 8)

If I have a Uniserve service that I've created, and two clients (say, 
A and B) connect to this service, how can I have A send a message 
to B?

Basically, I need a way to do client to client communications with 
Uniserve, much like say a chat server.

In your Uniserve service, build a list of ports with every client 
connecting (on-new-client event). When required, walk through the 
list of ports and broadcast whatever you want to the selected ones 
(or everyone). See this Chat application server-side source as an 
example of how to achieve that (it's not an Uniserve service, but 
it's very close anyway) : http://cheyenne-server.googlecode.com/svn/trunk/Cheyenne/www/ws-apps/chat.r


The resulting chat application is here : http://demo.cheyenne-server.org:8080/chat.html

One question Doc , I know you invested a tons of time info figuring 
out all thinks needed to make async sockets with rebol work so well, 
but..  did you ever consider using something like libevent ( http://www.monkey.org/~provos/libevent/
) or libev ( http://software.schmorp.de/pkg/libev.html) . These 
libraries are very popular with embeding in many languages ( and 
show outstanding benchmarks ) last few years after the C10K problem 
was formulated ( http://www.kegel.com/c10k.html)

I am asking just out of curiosity and because it could mean aditional 
benefits for uniserve (which I am looking to use for sometihng now) 
and by that of course also cheyenne

Libevent were suggested for R3, to be incorporated, but Carl said, 
that event model was rewritten for R3, and that it is really good. 
IMO Uniserve is relying on R2 even mechanism, I am not sure how it 
could use libevent instead? But that is for gurus to consider ..

I'm aware of libevent. Wrapping such lib in R2 would mean, at least, 
giving up on REBOL ports and REBOL's event loop. Quite a huge price 
to pay (UniServe couldn't be used with View apps, nor could receive 
system:// port events anymore). There's also the need to call REBOL 
function from the C side, which is not well supported in R2 (not 
even in R3...yet).

I also don't know. I suppose it would mean to change the rebol event/async 
handling with this. I know this would be a huge decision so I am 
not expecting any answer or anything.. just wanted to put into discussion

Aha .. cool ..