World: r3wp

nope.  didn't know you had released them.  I was aware that you had 
been working on something.

they are not entirely done, but doc uploading and syncing should 
work.

so it should be possible to create a local editor to edit mediawiki 
pages, or to upload series of pages generated locally.

new-line post from ML: http://www.rebol.org/ml-display-thread.r?m=rmlMMCC

Looks like I need to do a HTTP PUT to upload binary files ....

So, I guess I need a way to add the PUT method, and then switch the 
IO from lines mode to binary and then back again.

From my understanding,  R3 implements http prot all as binary and 
does not use lines mode

yes, R3 tcp ports are binary only.

So, how about something like  read/custom url [ PUT %file [ header 
.. ] ] ?

calculate the content-length, add the new headers, insert the file 
as binary and then switch back to lines mode for R2 ?

apart from it not working ... anyone see a problem with this?


   either all [block? port/state/custom post-data: find port/state/custom 
   'post post-data/2] [
				http-command: "POST"
				HTTP-Get-Header: make HTTP-Get-Header append [

     Referer: either find port/url #"?" [head clear find copy port/url 
     #"?"] [port/url]
					Content-Type: "application/x-www-form-urlencoded"
					Content-Length: length? post-data/2
				] either block? post-data/3 [post-data/3] [[]]
				post-data: post-data/2
			][

    either all [block? port/state/custom post-data: find port/state/custom 
    'get post-data/2] [
					http-command: "GET"
					HTTP-Get-Header: make HTTP-Get-Header append [

      Referer: either find port/url #"?" [head clear find copy port/url 
      #"?"] [port/url]
					] either block? post-data/3 [post-data/3] [[]]
					post-data: none
				][

     if all [block? port/state/custom post-data: find port/state/custom 
     'put post-data/2] [
						http-command: "PUT"
						data: system/words/read/binary post-data/2
						HTTP-Get-Header: make HTTP-Get-Header append [
							Content-Type: "application/octet-stream"
							Content-Length: length? data
						] either block? post-data/3 [post-data/3] [[]]
					]
					post-data: post-data/2
				]
			]

last line should be 

post-data: data

And it's working :)

read/custom URL compose/deep [ PUT %file.png [ Cookie: (cookie) ]]


will use the http put method to upload a binary file and sets the 
cookie

So, this will work with large files, it should be changed so that 
it does a skip/binary and inserts the file in chunks.

If the server returns an error such as 400 bad request, Rebol appears 
to discard any messages that the server sends back with this .... 
and just throws an error.

Wouldn't it be better if we had access to the data sent to us without 
doing an 'open instead of a 'read ?

This is pretty cool .. I just uploaded a 14Mb file using PUT ( though 
I had to increase the http timeout period )

Seems odd to me that the port will timeout even though it "knows" 
it is writing data to the port.

Here's the protocol with my changes ..

http://rebol.wik.is/Protocols/Http

file: replace/all file {®¯} {}


Why can't rebol replace that string in the file I'm processing?  
It will replace it in a string entered at the command console, but 
not in my file.

file: read %file.txt

it's better to do it on a binary representation of the string, using 
'as-binary. the chars you enter in console may not be of the same 
charset as those you have saved the file in.

Like this?

file: replace/all file as-binary {®¯} {}

Henrick, from what you say, I think I see what is happened. I'm copying 
the string from a utf-8 encoded file to an assci encoded file. The 
copy converts the string to different characters. But how do I get 
around this?

is happened = is happening

you must work solely from the encoding in the file. intermixing input 
from the console will ruin that. I will post an example in a minute.

or easier for me to explain: you must search for the hex values in 
the file. work only in binary.

what I would do is get the offending chars from your file in a text 
editor and paste them in a separate file and save it in the same 
encoding as the original file. then read/binary it with rebol, and 
you can see the hex values directly.

Graham, in R3's http you can use any method you want, with any headers 
you want and any content you want. Was this your question? (I do 
still need to add transparent cookie support. but that's a few minutes 
work, so it'll be there for release.)

Henrik, that worked. Many thanks!

congrats :-)

Gabriele ... I probably did ask that question and it's good to know 
the answer is affirmative.

But since we are stuck without R3 at present, I'm needing to patch 
the R2 prot-http so that we can use all the headers.

methods.

What's the situation with timeouts in R3?

not too good yet. but, i know Carl has that internally, it's just 
not exposed.

has the forward recursion problem from http been fixed in R3 ?

The HTTP handler and the entire port model is completely different 
in R3, so they have almost no code in common. R3 will have an entirely 
new set of bugs to worry about :)

that's very reassuring Brian.

Here's something to reassure you: Gabriele wrote the HTTP scheme 
for R3.

Don't worry about the port model changes - the new model is much 
better.

Yes, I saw it .. didn't understand a thing as usual!

What I was wondering though was, why should a protocol timeout even 
though it is still actively communicating ie. sending data to a port?

and presumably receiving acks back

Don't presume, check. If you don't get the ack in time, timeout.

I haven't written a network protocol in either port model yet (just 
studied them), so I can't say why you are getting timeouts in this 
particular case though.

Later...

load/all: Does this skip everything until a REBOL header is found?

No -- /all assumes all text is data and that the header, if present, 
is two more values.