World: r3wp

Busy, I am ;-). But there's a new version sitting on my hard drive 
which could be useful to some people here.

no one there though

what are the arrows for?

You can move the yellow boxes:-) and all you say is visible here 
as well - http://www.informacezbrna.cz/

yee gods .. .birds attacking me!

And the people talking now are puppets - they are recitating Plato's 
Gorgias

bots

Just one - I'm sending it from my computer to the server

At this moment I'm able to connect it event with IRC servers, but 
I do it know just from home

Oldes, cool design !

I want do do more with it - this is just a test

Doc, any updates on sending encrypted files ?

new flags on signalling end of file transmission?

I've added a new event : 'on-write-chunk to allow modification of 
the chunks of big files just before they are sent. This can be the 
hook to implement compression or encryption when sending big files.

Great.

Adding an appropriate header and decoding it on the other end is 
still up to the programmer. (Same for adding some flags to signal 
start / end of transmission).

Btw, this new event is untested yet. I should be able to provide 
you a small prototype service and client protocol to show you how 
to use it.

that would be necessary :)

It could be quite simple in fact (at least in theory) :


1) Send a first message telling the name and size of the file (unprocessed) 
to transmit
2) Send the file in parts (done automatically by Uniserve)

3) Catch the 'on-write-chunk event to process the chunk data (compress, 
encode...) then add a header containing :
     - size of the chunk

     - a sequence ID (an incremental counter starting with 1, 0 would 
     mean last chunk)

Please find here : http://softinnov.org/tmp/UniServe0919.zipa snapshot 
version of latest UniServe sources. It fixes some of the issues I've 
been asked about (UDP support for example). It's a beta version, 
no updated docs, no samples. ChangeLog in %uni-engine.r file. Any 
questions ? Ask them here, I'll answer as my available time permits.

.

Hey Nenad..  Any encapping docs would be great.

And what exactlu do you want to know, just use #include instead of 
'do' and %prebol.r to build it.

but the modules are loaded when needed, so you should make some more 
improvements to make one-file build

Terry, with the release of Cheyenne (soon I hope), you'll get a complete 
working example of encap-fs library usage.

Cheyenne comes with sources? How is it different to Uniserve? Or 
is it just Uniserve based?

UniServe is a network programming framework. Cheyenne is web server 
(with lot of features) using UniServe as low layer.

Can I handle virtual domains with Cheyenne?

Sure

soon i hope too, Nenad

Any benchmarks would be helpful as well.

Need some help...Can't seem to get Uniserv working on my XP laptop. 
 This is my first try...so I don't have enough experience to see 
what is happening.  Do I have the wrong version of core?

>> uniserve/boot
[uniserve] Async Protocol Admin loaded
[uniserve] Async Protocol DNS loaded
[uniserve] Async Protocol FastCGI loaded
[uniserve] Async Protocol HTTP loaded

** Script Error: change expected series argument of type: series 
port
** Where: install-plugin
** Near: change pos/2 new
>>

what version you are using? and what if you probe the pos value?

I've tried all the versions with asych...but I haven't probed the 
pos value yet.

Working on something else at the moment, but very interested in the 
Uniserv implementation of MySQL.

Hi Scott, my fault, the release archive contains a duplicate HTTP 
protocol file, so they collide on loading. Just remove the following 
file : uniserve/protocols/HTTP2.r

The MySQL async driver in this archive is an alpha version. It only 
works with v5+ servers and new passwords format (databases with old 
passwords for users won't work with this alpha driver).

Ok...thanks.

Doc, do you continue to devleop Universe or is it that matured that 
it's just working?

Session is broken, lot's of usefull stuff not released (RPC, rebol-cgi, 
fast-cgi, PHP) ....

it states stable, but it really is not. Doc, before he left scene 
for another few months :-), stated something like that he has new 
reimplemented session handling, which is going to be "soon" released. 
But don't take it for granted, maybe I misunderstood something. But 
really - sessions do not work properly ... There is a demo with multiple 
frames, e.g. Mozilla (but even IE) did not open all boxes, there 
were some errors or timeouts, dunno ...

Ok, thanks for the info.

I'd say the core is actually stable, have it running with quite some 
traffic and no problems, there are indeed problems with sessions.

Had a sign very recently that let suppose Dock will soon be back, 
hopefully 8)

Will, if you have contact to conference organisers, please urge them 
to do something with DevCon preparation. Som of us have to plan our 
plane or bus few months ahead. I would like to see site updated ...

Uniserve doesn't do session handling, Petr. You are probably thinking 
of Cheyenne, which is built on Uniserve.

I may be mistaken though...

you are right! Cheyenne is the http 1.1 webserver

Pekr: have forwarded decon07 update request.

wops, devcon07 ;-)

see related post wrt async dns in the core group. Is the behavior 
mentioned in the core group possible with Uniserve async dns support 
 ?