World: r3wp
[!Uniserve] Creating Uniserve processes
older newer | first last |
Scot 1-Oct-2006 [378] | 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 >> |
Oldes 2-Oct-2006 [379] | what version you are using? and what if you probe the pos value? |
Scot 2-Oct-2006 [380x2] | 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. | |
Dockimbel 3-Oct-2006 [382x2] | 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). | |
Scot 4-Oct-2006 [384] | Ok...thanks. |
Robert 6-Jan-2007 [385] | Doc, do you continue to devleop Universe or is it that matured that it's just working? |
Pekr 6-Jan-2007 [386x2] | 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 ... | |
Robert 6-Jan-2007 [388] | Ok, thanks for the info. |
Will 6-Jan-2007 [389] | 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) |
Pekr 6-Jan-2007 [390] | 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 ... |
BrianH 6-Jan-2007 [391x2] | Uniserve doesn't do session handling, Petr. You are probably thinking of Cheyenne, which is built on Uniserve. |
I may be mistaken though... | |
Will 6-Jan-2007 [393x3] | you are right! Cheyenne is the http 1.1 webserver |
Pekr: have forwarded decon07 update request. | |
wops, devcon07 ;-) | |
Joe 12-Jan-2007 [396] | see related post wrt async dns in the core group. Is the behavior mentioned in the core group possible with Uniserve async dns support ? |
xavier 12-Jan-2007 [397] | rebol server pages ? will we have samples of it ? |
PeterWood 12-Jan-2007 [398] | Does this help ? http://www.ross-gill.com/techniques/rsp/ |
Maarten 13-Jan-2007 [399] | Ah.... those were the days |
xavier 13-Jan-2007 [400x2] | i just installed cheyenne and tried to explore it ... i found the examples |
very interesting tool ... i go to do a site on it | |
Joe 14-Jan-2007 [402] | 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 !) |
Maarten 14-Jan-2007 [403] | They are all 3 abstractions of a lower-level rebol async layer, performance is in the same range. |
Mchean 25-Jan-2007 [404] | I've received an error in starter.r: ## Error in [uniserve] : Cannot open server HTTPd on port 80 ! |
Pekr 25-Jan-2007 [405x2] | 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 ... | |
Mchean 26-Jan-2007 [407] | Thanks Pekr, that would be a suprise if i was running a server somewhere |
MikeL 26-Jan-2007 [408] | Easy to check with http://localhostSometimes that gives you the home page of the server that is colliding with the one you want. |
Oldes 27-Jan-2007 [409x2] | 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:( | |
Mchean 29-Jan-2007 [411x2] | 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. | |
Graham 29-Jan-2007 [413x3] | open Rebol |
try : server: open tcp://:80 | |
if that fails, then another process is serving on 80. | |
Pekr 29-Jan-2007 [416] | 0.9.9 is latest official version. But scroll to some earlier messages here, and you will find link to beta 0.919 version .... |
Mchean 29-Jan-2007 [417x2] | thank-you! |
Would there be any issues with port blocking in Windows XP and their firewall? | |
Graham 29-Jan-2007 [419] | XP will ask you if you start up a server process if it is to be allowed |
Mchean 29-Jan-2007 [420] | 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. |
Graham 29-Jan-2007 [421x3] | 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 | |
Pekr 29-Jan-2007 [424] | netstat -an |
Mchean 29-Jan-2007 [425x3] | 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 | |
older newer | first last |