[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
>
> > This also points to a potentially larger problem in
> > that Rebol doesn't appear to handle any protocol
> > not based on TCP. And unfortunately you can't create
> > your own sockets (to do a ping you need a different
> > socket type than TCP) which means no UDP broadcasting/
> > multicasting, etc. can be done. This is one area
> > that I would like to see /Core improve on (and I would
> > really like to see it as /Core, NOT /Command). But yes,
> > you can use /Command to call into your own ping function
> > if you had to.
> >
>
> "I believe IRC uses UDP which should be fully supported very soon." - Those
> were the words of Bo some time ago :-)
> As for /Core, - yes, it should be part of it if implemented.
>
> btw: I've heard UDP is used for Ethernet? Is it right?
I have found another earlier comment from Jeff :-)
-------------
> [EMAIL PROTECTED] wrote:
> Aha, so I missunderstood you, is it possible to udp talk with
> current version of port implementation?
Yep:
close insert open udp://somewhere:9090 "something"
and "something" will, infact, be sent via udp to somewhere's 9090
udp port (which I verified earlier today). For some reason it doesn't
seem possible to create a udp listen port, though. I don't think, or
at least never heard that anyone had ever really verified the udp
stuff before (due to udp's lack of popularity I suppose) so I thought
I'd take a peek it at. I think the problem with the udp listen ports
is in the port interface. Perhaps they can be fixed before the next
release.
---------
-pekr-
>
>
> -pekr-
>
> >
> > Rodney
> >
