World: r3wp
[!Cheyenne] Discussions about the Cheyenne Web Server
older newer | first last |
james_nak 12-Feb-2010 [7907] | Doc, I wonder if that is my problem. I don't have worker-libs my httpd.cfg file. |
Dockimbel 13-Feb-2010 [7908] | James: it's not mandatory, you can load mysql driver from 'on-application-start event for example (but you'll need to do that for all your webapps). It's just simplier to declare it in config file once for all. |
james_nak 13-Feb-2010 [7909] | Got it. |
Carl 13-Feb-2010 [7910x2] | I want to move DevBase (R3 Chat) to Cheyenne, but I must admit that I am a newbie with Cheyenne. Currently the code runs as a process, and we tunnel packets thru HTTP via Apache. However, I could run it as a persistent process in Cheyenne, or via some method that would simply put the http input and output into a socket. Anyone here know how this is done? |
(BTW, I'm doing this to move DevBase to the new Linnode server... to offload it to a faster location.) | |
Graham 13-Feb-2010 [7912] | Is this why chat is down now? |
Carl 13-Feb-2010 [7913] | I've not shut it down yet. But, I've been having difficulty connecting to that server all day. It's probably under 10 feet of snow. |
Graham 13-Feb-2010 [7914x2] | If it's running as a single process .. that won't scale very well will it? |
Wonder how much slower it would be if you ran it as rsp scripts | |
Carl 13-Feb-2010 [7916] | It scales very well... as long as it has a web server sitting in front of it. |
Henrik 13-Feb-2010 [7917] | as a cheyenne app it probably would run faster |
Carl 13-Feb-2010 [7918] | The web server does the serializing and I/O buffering. |
Graham 13-Feb-2010 [7919] | If you ran it as rsp, it wouldn't be serialized |
Carl 13-Feb-2010 [7920] | Basically, it does not matter where the proc lives, as long as I can "redirect" I/O to it from the web server, which does all the TCP buffering. |
Graham 13-Feb-2010 [7921] | where's the server code ? |
Carl 13-Feb-2010 [7922x2] | Basically, what I want is this in raw binary I/O: print send-to-proc tcp-port input |
I can write a CGI to do that, but it will be slower because it requires an extra CALL from cheyenne. | |
Graham 13-Feb-2010 [7924x2] | rsp doesn't use an extra call |
it uses one of the existing rebol processes to deal with it | |
Carl 13-Feb-2010 [7926] | Does rsp run in binary port mode? |
Graham 13-Feb-2010 [7927] | It must do if it accepts binary uploads |
Carl 13-Feb-2010 [7928x2] | Ok, so via RSP, I can use request/posted to get the input cotent. That's good. |
So, I guess a short RSP should do what I need. | |
Graham 13-Feb-2010 [7930x2] | if you want to let users login, then you need to track a session cookie |
And then you can run everything as a Cheyenne webapp | |
Carl 13-Feb-2010 [7932] | This is for R3 Chat, not web. Session management is already there. I'm simply using a port 80 tunnel. |
Graham 13-Feb-2010 [7933] | webapp just gives you session management with authentication, doesn't mean it is web |
Carl 13-Feb-2010 [7934] | Ok... got a one line RSP that works for this: >> to-string second load write http://host4.altme.com/echo.rsp"testing" == "testing" |
Graham 13-Feb-2010 [7935] | >> r: second load read/custom http://host4.altme.com/echo.rsp[ POST "testing" ] connecting to: host4.altme.com == testing |
Carl 13-Feb-2010 [7936] | Got it! >> to-string write http://host4.altme.com/echo.rsp"testing" == "data: testing^/^/" |
Graham 13-Feb-2010 [7937] | me too |
Carl 13-Feb-2010 [7938x4] | The "magic" RSP line is: <% insert tail response/buffer request/posted %> |
so, now, need to throw some binary at it.... | |
>> write http://host4.altme.com/echo.rsp#{0209103040508898af} == #{0209103040508898AF0A0A} Good to go. | |
Ok... basically got it working, but it's very slow due to hitting a timeout on each packet. | |
Graham 13-Feb-2010 [7942x2] | Why is it timing out? |
And is this a http timeout or a cheyenne timeout? | |
Carl 13-Feb-2010 [7944x2] | The core of the problem is that SET-MODES port [close: false] is not supported in 2.7. Without it, we cannot close half of the duplex socket. |
In other words, there is no socket shutdown() function. | |
Graham 13-Feb-2010 [7946] | so the client times out ... |
Carl 13-Feb-2010 [7947x3] | The server's input request packet times out. |
Ok, no problem... will add content-length field. Shouldn't take much time. | |
So, R3 Chat server has been moved to Dallas TX running in Cheyenne on a cloud. | |
Graham 13-Feb-2010 [7950] | Not logging in though |
Maxim 13-Feb-2010 [7951] | working for me. |
Graham 13-Feb-2010 [7952] | --- Note: login initiated *** RebDev Error: server connection failed, is server down? (server-failed) |
Maxim 13-Feb-2010 [7953] | probably a DNS issue... he has changed servers... so the IP surely has changed? |
Graham 13-Feb-2010 [7954x3] | POST /cgi-bin/rebdev HTTP/1.0 Accept: */* Accept-Charset: utf-8 Host: host.rebol.net User-Agent: REBOL Content-Type: application/x-www-form-urlencoded; charset=utf-8 Content-Length: 56 [0.4.0 "Graham" password login]HTTP/1.1 500 Internal error in REBOL CGI Proxy Date: Sun, 14 Feb 2010 02:05:45 GMT Server: Apache/2.0.53 (Fedora) Content-Type: text/plain; charset=UTF-8 Via: 1.1 bc7 Connection: close Cannot connect (3) |
I believe it has shifted from rebol.net . | |
Found the issue ... http://www.rebol.com/r3/chat.rwas being cached. Refreshed it in my browser until I got the new version and now it is working again. | |
older newer | first last |