World: r3wp

To me, it almost looks like things aren't working "as advertised", 
which may be because docs and code aren't properly sync'ed.

Graham: I suspect that your problem is simply that you have to wait 
on all the ports (including events), not just the network port. Don't 
forget that R2 has a "hidden" list of extra ports to wait for (system/ports/wait-list), 
while R3 does not AFAIK

Yes, that's what I'm after, Gabriele. Opening a network port and 
then waiting for network, time, or gui events.

Christian: does the example on the wiki work? If not, then something 
has been changed since then, and I can't help much without studying 
everything back again. If so, then maybe we can figure out why your 
version does not work.

studying your own code ?  :)

ie. this one:

   port: make port! http://www.rebol.com/
   port/awake: func [event] [
       switch event/type [
           connect [read event/port]
           done [print copy event/port return true]
       ]
       false
   ]
   open port
   wait port

Graham: mostly, the changes in R3, and trying to figure out how it 
works now. It's not like there are docs with enough details...

Gabriele, that's the main point of confusion to me, that even that 
example fails. I.e.. hangs when DONE, in the same way as my attempts 
on this.

Ok, so it's not your fault. R3 has changed and the HTTP scheme does 
not work correctly anymore.

Good to know. I like the line "It's not like there are docs with 
enough details..."

I think I read somewhere Brian saying that http had to be modified 
as chunked encoding didn't work or something like that

But the source was modified and not the rlp

IIRC http was degraded to 1.0 from 1.1 due a problem Graham describes 
...

Isn't there a source code revision history somewhere??

so we can see exactly what was changed?

Looks like we need a set of unit tests for the protocols ...

All changes to the source are in DevBase.

devbase??

last contribution to devbase was 1 mar 2009 by yourself

More likely than changes to the http-prot source being the reason 
for the async behaviour not working as expected are changes to the 
core itself.

That's my guess.

I tried against Gabriele's original pto-http sources as from the 
*.rlp, not the *.r as touched by Carl. Only thing I changed was two 
replacements of THIRD with BODY-OF.

No luck even with older R3 versions; version 2.100.33.3.1 dating 
back to 2009-01-28 being the oldest I have around.

*pto-http = prot-http

Graham, all changes to the prot-http sources seems to be authored 
by Carl, I've seen no traces of changes to the protocol introduced 
by Brian.

Andreas and I did the same, doing a diff on the original prot-http 
and current and found no major changes.  Suggest submit a bug report.

DevBase is the forum/filestore that you access withg the CHAT command 
in R3.

I haven't posted changes to the http protocol yet, sorry.

Brian, I guess you are talking about changes that are also not yet 
in R3?

Ah, nevermind. Upon re-reading, I think I misunderstood your message.

Right. The http scheme is due for a major revamp. What we have is 
not really all that we want.

So we now have two DevBases ?

Technically, the one accessed through CHAT is the third DevBase. 
The other two have been retired.

The first was written by Carl to do /View development, way back when, 
and never released (afaict). DevBase 2 was derived from that, and 
DevBase 3 was based on the lessons learned from 2.

Ok, we need to be more explicit and refer to DevBase3 now

It's the only DevBase now. I just use the term to distinguish from 
CHAT, which is only a mezzanine that calls a DevBase client. Most 
people just call it chat.

So we have the datastore (DevBase), the server (DevBase server), 
a client (DevBase client) and the mezzanine wrapper (CHAT).

For most people those distinctions don't matter, they can just call 
it chat. It matters to me because writing another DevBase client 
is on my immediate todo list.

I client for R2, to be accessed through a CHAT mezzanine in R2.

I -> A

Updated Feb 21 http://github.com/gchiu/Rebol3/tree/master/protocols/

thanks for this Graham

I want to build a very very very simple web server in R3.

I just want to be able to receive an HTTP request and send the response.
But me and Rebol networking are two differents people !!


To begin, I just want to be able to display the full request in the 
response page.

So far I have wrote this by peeking code in DocBase, but it does 
not work as I want : the browser stay awaiting the answer. Can one 
point me to what's wrong ?

REBOL []

print "Serving port 8080..."

open-subport: func [port] [
    print "=== Creating sub-port"
    port/awake: func [event /local port] [
        print ["=== Subport event:" event/type]
        port: event/port
        switch/default event/type [
            read [
                print ["    " data: to-string port/data]

                write port to-binary rejoin ["<html><head></head><body>" data "</body></html>" 
                newline]
                true
            ]
            wrote [read port]
            close [close port]
        ] [false]
    ]
]

server: open tcp://:8080

server/awake: func [event] [
    print ["*** Server event:" event/type]
    if event/type = 'accept [
        open-subport first event/port
    ]
    false
]

wait 30
close server
print "Done serving"
halt

Seems I have found my way to make it working :

REBOL []

print "Serving port 8080..."

open-subport: func [port] [
	print "=== Creating sub-port"
	port/awake: func [event /local port data] [
		print ["=== Subport event:" event/type]
		port: event/port
		switch/default event/type [
			read [
				print ["    " data: to-string port/data]
				data: replace/all data newline <br>

    write port to-binary rejoin ["HTTP/1.0 200 OK^/Content-type: text/html^/^/<html><head></head><body>" 
    data "</body></html>" newline]
			]
			wrote [
				close port
			]
		] [false]
	]
	
	read port
]

server: open tcp://:8080

server/awake: func [event] [
    print ["*** Server event:" event/type]
    if event/type = 'accept [
        open-subport first event/port
    ]
    false
]

wait 30
close server
print "Done serving"
halt

great!

You might also want to have a look at: http://github.com/earl/rebol3/blob/master/scripts/shttpd.r

Ah, you just forgot the http header.

Thank's Anton. Can be of some help.