Hello Rebol Guru,
( Ill address directly :-)

When a port is opened or closed or data is sent or incoming
i see diferences in the state object! of that specific port.

I would be such a relief to know that I could read usefull
information form the state: opject! or it would be very usefull
to know that its of no use to know anyway ;-)



Please explain to me the variables possible for -->>

 state:
    make object! [
        flags: 1024
        misc: [116 [] 0]
        tail: 0
        num: 0
        with: "^M^/"
        custom: none
        index: 0
        func: 3
        fpos: 0
        inBuffer: unset
        outBuffer: none
    ]



So far :flags tell me the following ==>

(Well dont tell use that we should not mess around with the
flags because these are trackable...uhum...and as it seems 
now not even that secret...BUT what Im wondering about..
can we track a open? or close? on these flags??? 
regarding the listing below is wrong ;-)


flags:
== 4719107 when tcp opened (default /string /direct )
== 4719139 when tcp opened /binary
== 4719171 when tcp openen /lines
== 4719106 when tcp opened /write
== 4719105 when tcp opened /read
== 4721155 when tcp opened /no-wait
....
....
....
== 524803  when tcp input recieved from remote
== 1024    when tcp closed 


The rest below is guessed..adjustement is very welcome..

func: 
== 6 and 3 seen, probably to differentiate port use .. url file console.. ???


misc: 
== ????


tail:
== probably used for files


custom:
== for custom opening a port


index:
== ??? index of the buffers????


fpos:
== ??? file position ???

inbuffer:
== IO

outbuffer:
== IO




A Rebolish Thanks,
(R)egards,
Norman



-- 
Conversation/lunch: "How do you Eat your Rebol in the Morning?" 





-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to