World: r3wp

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

And if you are using the Uniserve from the link above, you should 
know, that it's just a shapshot from doc's folder so you have to 
for example edit some files - for example the default prefs of the 
HTTPd as they are leading into files which don't exists.

Not really, just trying to get the out-of-box experience

hmm... maybe that's not a good expectation then

my purpose is to educate myself about servers using Uniserve as a 
starting point

just go to services/HTTPd.r file and edit the prefs

you can also change the port you are listening - for example to 8080

the file is probably not in the best shape as there are some probes 
which are probably because of debugging which was Doc making at the 
moment when he gave it here

ok thanks - do you think Rugby might be a better choice?

I don't know, I never used Rugby and don't know what you want to 
do:)

just a learning tool

what kind of learning?

I started with uniserve 0.9.9 which is stable enough for me.

to learn about web servers, and rebol commands

I'm not sure if you should not start with some older server which 
are not async

for example with this one http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=webserv.r

thanks - i will look at that

And there is another bug in the UniServe0919 - there should be this 
in the file %services/task-master/task-handler.r (the [not value?] 
check is not enough):

if any [not value? 'uniserve-path none? uniserve-path] [uniserve-path: 
what-dir]

if any [not value? 'modules-path none? modules-path]   [modules-path: 
dirize uniserve-path/modules]

if any [not value? 'uniserve-port none? uniserve-port] [uniserve-port: 
9799]

Oldes, why don't you release a fixed version ?

I just started:)

and still have some problems...

That all sounds really strange, as Doc was claiming they use Uniserve 
in production for several customers or so, for quite some time ...

Oldes - what does your task master fix fixes particularly?

Mchean - In the past I really loved Rugby - if you want to start 
with something, and learn something (RPC), it is really a good choice 
(Rugby). Very simple to use. What I did not liked was - its lack 
of asynchronicity. E.g. in Rugby you select your function of exported 
(so callable over the tcp/ip network). But if such function does 
something for 10secs, then all Rugby is blocked and it is not able 
to accept further requests.