World: r3wp

Should be enough

make-scheme [
	title: "Dns"
	name: 'dns2
	actor: [
		read: func [port [port!] /con][
			con: open [scheme: 'tcp host: port/spec/host]
			con/awake: func [event][true]
			wait [con 5]  ;*** timeout 5 secs
			attempt [get in query con 'remote-ip]
		]
	]
]
>>read dns2://www.rebol.net
216.240.11.203

Thanks Steeve!

not that i don't need to close the tcp port because it is not (really) 
opened yet

not=notice

I didn't open the port either

Normally one would open the port in the lookup event

yep

Andreas likes to use funct so no need to declare the locals

Now how to do a reverse dns lookup??

i don't have any idea how to do that

>>read reverse dns2://216.240.11.203
www.rebol.net

oops ... someone made this group web public!

ahah

we can change it back ...

the above was a joke!  please ignore

reverse lookups http://cr.yp.to/djbdns/intro-dns.html

IIRC we need UDP to do a DNS request.

So that we can't currently

Yeah .. just did a packet trace and it's all UDP

R3 does not contain UDP in networking device low level code?

not yet

Steeve, what's the algorithm for reading data from a port when you 
don't know how much data is coming down?

Does each arrival of data trigger a 'read event?

and does it append to port/data ?

some internals on how low level networking code works - http://www.rebol.net/wiki/TCP_Port_Details

yep graham

# Setup the IO-request data and length fields. Data is the buffer 
tail position. Length is the buffer space available from above. Clear 
the actual field.

so it does an append

but don't forget to execute a [read port] each time you received 
a packet , to be able to receive the futher one.

so you need to do a read port inside the read event?

yep

all this word overloading drives me crazy!

packet are append to port/data but the index is not moved

eh?

so how to read until there is no more data ?

no "eh?" me !!!
:-)

so the index is used by ??

there is no way to know how much packets can be received.
Your protocol has to send this info, if not you're tricked

why should every data be read first? Why is not 'read even triggered 
on new data arrival = change of buffer size?

actually the read function ask to the server to send the next packet 
to the client, if any.
You may receive a packet (event read triggered) or not.

Do we need to clear the port data after a read ?

or before a read ?

eg. copy port/data clear port/data read port ?

you do as you want

the packet is added to port/data

so if we 

copy port/data read port copy port/data .. we will get duplicate 
data ?

yes

ok.

so no more data is appended to the port/data until we ask for it 
using a read port

it's your duty to clear or remove/part data in the buffer