Dear Ryan,
I understand what you are saying, but...
There is a vast installed base of dumb capital that likes to talk serial
communication.
It would seem prudent to leverage what we have all payed for and already own in
the way of infrastructure by bridging the gap with some fresh code that is
relevent to the new direction things are taking and binding it to some off the
shelf hardware that has been around for 20+ years and is fully debugged. This
stuff has already been wired so why does it need to become unwired suddenly. The
code is the transcendant aspect that imparts value. The investment in new
hardware should come after we have enhanced local data before injecting it into
a finite and premium channel. Tcp and wireless communications have very high
overhead which should not be wasted monitoring the light in your fridge and the
fullness of your cats litter box just because you're able to do it with wireless
Tcp. There is a reason why a healthy mind is so impervious to self awareness.
The shear din of its' minutiae would force it to its knees. Why should applied
networking behave any differenty?
Latin dprecr, dprect- to ward off by prayer: d-, de- + precr, to pray; see prek-
in
Indo-European Roots.]
Perhaps your choice of words has a hidden element of truth. The absence of
penetrating thought has perhaps left the eqation a little unbalanced in favour
of the new.
Just a thought.
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
> Perhaps the thought is that COM port addressing has already been
> deprecated in favor of tcp/ip addressing to wireless devices?
>
> -Ryan
>
> >
> > Thanks for the pointer Brett.
> >
> > Seems a little odd that a "messaging system" would not be inclined to talk
> > or at least listen to something as fundamental as a com port. Think of all
> > the serial devices hanging off the end of PCs that need monitoring in real
> > time. Given that I just "discovered" (thanks ddj) Rebol perhaps there is
> > something I am missing?
> >
> > [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> > [EMAIL PROTECTED] wrote:
> >
> > > My understanding is you cannot access the com port directly from Rebol.
> > > However, I used IPComserver a program by http://www.iox.co.za to
> > > essentially give the Com port a tcp/ip port. Then I could use Rebol with
> > > tcp/ip through IPComserver to talk to my device.
> > >
> > > Brett.
> > >
> >
