World: r3wp

Why this function runs well on some web servers (f.ex. KFWS) but 
hangs (getting cgi script time out) for MS IIS and how to solve them? 
I found that problem is in line where read-io is.

read-post-data: func [
    {Reads the HTTP entity body}
    /safe "Disables evaluation of content-length header."
    /local len data tmp
] [

    len: load any [ all [safe "65536"] system/options/cgi/content-length 
    "0" ]

    data: make string! len
    tmp: make string! len
    while [ 0 < read-io system/ports/input tmp len ] [
        insert tail data tmp
        clear tmp
    ]

    data
]

REBOL, being targeted at higher level use, hasn't made bit twiddling 
terribly easy in the past, to be sure, but if you're doing a lot 
of it, write a dialect. :-)

Maxim, yes the byte order is dependent on the platform.

Janeks, try 
	set-modes system/ports/input [binary: true]
before the WHILE. Maybe it works ?

Anton, it did not help!

How the MS IIS is putting  those cgi data into system/ports/input?

I got two REBOL functions, say, f1 and f2, which are both time-consuming.

How can I make them run simultaneous in the same process? Thank you.

Got the answer as "NO", form the REBOL mail archive in REBOL.org.

Janeks, I don't know, I'm sorry. I've never used MS IIS.

Jerry, yes, you will have to divide the work up into manageable chunks.

ladislav, I'm becoming comfortable with BUILD. it is indeed very 
nice to do evaluations "on the spot" inside large blocks.

guys, please, just introduce syntax, which will be in-build in R3. 
Because we are relatively close (well, who knows :-) to R3 alpha, 
and once we become familiar with some technique, I would not like 
to learn new habits for R3 eventually .... :-)

Jerry, can't you launch them in seperate processes?

BrianH, launching them in different processes is my second choice, 
How do i do that? By using the LAUNCH native function, right? I've 
never used it before. I will give it a try.

I have noticed some REBOL experts designing their own protocols, 
which, by the way, are very cool. By "protocol," I mean the protocol 
part of an url, it doesn't have to have anything to do with networking. 
I would like to design my own protocol, too. So I can write:

>> print read DICT://English/English/Cheyenne
Cheyenne
-noun, plural -ennes, (especially collectively) -enne for 1. 

1. a member of a North American Indian people of the western plains, 
formerly in central Minnesota and North and South Dakota, and now 
divided between Montana and Oklahoma.  

2. an Algonquian language, the language of the Cheyenne Indians. 
 
3. a city in and the capital of Wyoming, in the S part. 47,283.  
>>


Is there any document I can read about this. Thank you for your help.

your definition is missing the REBOL web server from DocKimbel ;o)

My mistake. Sorry, DocKimbel. And thank you for bringing us the wonderful 
Cheyenne web server

Jerry, go to 
http://knowngood.com/rebol/
and search "rebol scheme handler"

The first link for me is "Rebol Forces — Writing your own Protocol 
Handler" which as I remember is written very well by Jeff Kreis.

ah, Jeff Kreis, Holger Kruse, those were the times :-)

and be prepared to get your hands pretty dirty writing scheme handlers. 
You will need to understand how words are bound to different contexts. 
However, your scheme looks pretty easy to write.

(I mean, looks pretty simple, so *easier* to write.)

Thanks, Anton.

I have used   data: read/binary url   and saved data to disk. Now 
I want, without accessing the disk again, to translate the line terminators 
as if I had just READ the file at the beginning.
Any ideas ?

(I think I hit this problem already a long time ago..)

Is it as simple as this?
 data: read/binary http://www.rebol.com
to-string data

if you want to strip the CRLF form (which is what I guess you are 
trying to do:

data: replace/all to-string data "^M" ""

this will remove any CR chars hanging around after the to-string...

Hmm.. can't be a simple as that. I think READ determines the file's 
host platform somehow and translates accordingly.

rebol only strores newlines using the LF char internally (like unix)

Yes......

so the above will read DOS and UNIX newlines.

I'm using it myself for http operations on a server.  and it works 
flawlessly.

Mac uses just CR.

yes, but then how to determine the input itself.

Let me just see what to-string does...

if you have a potential for receiving Mac Files... (I was just about 
to give you this when you posted about mac ;-)

if converts byte for byte each char in the binary string;...

I have been handling binary data now for the last 2 weeks in many 
different operations.

for a more unified conversion you could do this:


data: replace/all replace/all to-string data "^M^/" "^/" "^M" "^/"


this way if its CRLF it will strip them and if its only CR it will 
convert them.

That looks better.

(Yes, looks like to-string doesn't really do anything except change 
the datatype from binary to string.)

that's a good thing.

otherwise, some operations within rebol would be just to crazy to 
handle.

working on EDI data, for example, the binary data is converted to 
string by PARSE... so if it tried to "fix" stuff, I could not properly 
parse it...  :-(

and EDI uses non-printable characters as separators...

and btw, I love REBOL's extended character set for words.  being 
able to use - + = ' &, etc in words just makes words so much more 
expressive.

I just discovered this week that we can use the tick in words!

Yes, pretty handy sometimes.

as in :

value': 99

so this allows us to define words which pretty much equate to themselves. 
 

blue': 'blue

hehe