World: r3wp

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 
 ?

rebol server pages ? will we have samples of it ?

Does this help ? http://www.ross-gill.com/techniques/rsp/

Ah.... those were the days

i just installed cheyenne and tried to explore it ... i found the 
examples

very interesting tool ... i go to do a site on it

How does uniserver tcp async compare with a) async://, b) atcp:// 
and c) the new async core that may eventually be released (and was 
available two years ago !)

They are all 3 abstractions of a lower-level rebol async layer, performance 
is in the same range.

I've received an error in starter.r:  ## Error in [uniserve] : Cannot 
open server HTTPd on port 80 !

Mchean - if you are using latest demo version, go to uniserve/protocols, 
and remove http2.r file - it was mistake of DocKimbel, who mistakenly 
left the testing file in the archive ...

and if it does not help, you are aparently running some web server 
on port 80 already ...

Thanks Pekr, that would be a suprise if i was running a server somewhere

Easy to check with http://localhostSometimes that gives you the 
home page of the server that is colliding with the one you want.

I started to play with the proxy-http service a little bit and found 
that there is a bug: the on-error http-event has args: [reason port] 
not [port reason] !

unfortunately there are still some issues with this service:(

Localhost doesn't respond in the browser, and there is no http2.r 
file andy other suggestions?  I'm have very little experience with 
servers so don't know where to startt

I'm using Version : 0.9.9  Date : 11-Oct-2004  is there perhaps a 
later version.

open Rebol

try : server: open tcp://:80

if that fails, then another process is serving on 80.

0.9.9 is latest official version. But scroll to some earlier messages 
here, and you will find link to beta  0.919 version ....

thank-you!

Would there be any issues with port blocking in Windows XP and their 
firewall?

XP will ask you if you start up a server process if it is to be allowed

Graham the command fails so i guess something has port 80 tied up 
though i don't know what this might be.  I've tried this on 2 pc's 
on one the localhost fails with no page found, and on another im 
prompted for a user password.  I'll talk to my tech.

there are windows utilities to see what ports are opened and by what.

netstat will tell you that 80 is open

try this http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx

netstat -an

i found this also on a suggestion from a friend:  http://www.hijackfree.de/en/

It turns out I have a inetinfo service running which locks that port. 
 Its used in IIS but since I'm not running it I'm not sure what is 
using this process, and killing it doesn't work, as it keeps coming 
back.  I will have to investigate using another port

scary how many open ports i have for processes i can't id

I figured out how to stop the service tying up the 80 port , When 
i run this is what I get: >> do %/c/temp/rebol/uniserve/uni-engine.r
== true
>> 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

does the binary work for you?

yes, i think im making progress thanks for the help

do you really need all the protocols? If not, you can start uniserve 
using this way:

do %uni-engine.r
uniserve/verbose: 5
uniserve/boot/no-loop/with [
	protocols [irc]
	services  [flashd task-master httpd]
]
;do whatever here
do-events