World: r3wp

Oh, and that means that the mezzanine is faster than the native :)

rare

Not really, for code that plays to REBOL's strengths. It happens 
quite often.

Rare for the kind of thing you tend to do though (emulators, iirc).

throw/catch does not work in R3?

Testing.

Bolek, THROW and CATCH work in R3 but there is a strange interaction 
with TRY.

How about we have some more refinements to read ??

Graham: my reply from R3 Chat:  I think that we will not get much 
refinements for read/write functions. The planned ones were /string 
(text) and /as (enconding). What you want is read working in a streamed 
way. We might get it in future, but I doubt we get what you propose.

Why not?  Because refinements slow down 'read?

And maybe design of read/write was never actually finished ;-)

16-Apr-2008: Prunning down read and write - http://www.rebol.net/r3blogs/0127.html

11-Nov-2009: Finalising read and write - http://www.rebol.net/r3blogs/0294.html

well, I guess we could specifiy it in the /as block

I don't know. Just read realated discussions - many opinions, what 
read/write should (not) do ...

I am with ones proposing having read/write as simple as possible, 
adding just /as for codec support. Codec API should be defined, the 
same way as we have Device API, port API, etc. /string should be 
no excuse .... in the past (1.2 days), Holger posted to IOS:

read http://something.com:my-callback

read/as ftp://ftp.rebol.com/matrix.avi[ file: %movies/matrix.avi 
]

and to resume


read/ask/seek ftp://ftp.rebol.com/matrix.avi[ file: %movies/matrix.avi 
 ] current-file-size-of-matrix.avi

hmm, but /as was proposed to specify just type of encoding IIRC, 
not some other functionality ... some of us wanted /as being more 
general, allowing you to specify a codec to decode. Codecs are so 
far inefficient (not streamed), because you have to read all data 
firts, then pass it to encode/decode.

Carl never posted a resolution to read/write case ....

Need some way to pass parameters to scheme actors.  Andreas is using 
read/lines !

I think my schemes are making R3 unstable.  Tried to post a message 
and got from chat


rebol system error #1301: invalid datatype 99 ... should never happen 
...

Well, we don't need of specific refinements, cause we can pass a 
block to read (which is converted to a port!).

>> read [scheme: 'ftp host: ... path:... other_data: ....]


The  block format could be used to pass other parameters in a more 
handy way.


>> read [ftp://ftp.rebol.com/matrix.avifile: %movies/matrix.avi]


And the good news, is that it's absolulty possible to have something 
like that now.
We just have to patch the function: system/intrinsic/make-port

Steeve - it is good we have you here :-)

btw - some time ago someone stated here, that current https scheme 
is done "old school". Was that you? Isn't now the right time to define 
the better way (if any) to aproach schemes and networking? :-)

Well, I am using a write spec block ...

sorry again (it's true i said this)

easy to talk hard to do

Steeve .. don't waste your time on a r2 chat .. there's no traffic 
on there.  Spend your time on schemes :)

We need a place to set a system timeout ...

To my mind, we need a better framework to design shames using a FSM 
dialect

shames=schemes

Like uniserve?

;-)

uniserve has some good ideas

Or do you mean use a dialect to define the scheme?

yes a dialect to construct schemes

meta programming

Rebol is especially good with those things

someone did FSM in the past. Gregg? Henrik?

Gregg

One from gabriele - http://www.colellachiara.com/soft/Misc/qml/fsm.rlp

Ladislav has done one too. Time for a FSM battle?

I suspect that you have to write a few schemes to see what is needed 
and then write the scheme dialect

yup we should start with the html one in R3, it's a huge one currently

Here's related ML discussion - http://www.rebol.org/ml-display-thread.r?m=rmlFDMJ

http://www.rebol.com/r3/docs/functions/write.html


says there is a /binary refinement .. but this doesn't exist any 
more

Graham, I'd do what you want with:

pipe ftp://somehost/somefile%/path/to/somefile

my implementation of PIPE is only a few lines. i think it should 
be native to R3.

my lower level is working like this

write port [ RETR "bigfile" %bigfile ]

how does switch on type? work?

switch type? %test.r [ .... ]

what do I need to write in the block to catch it ?