Ok, this replying to the individual is annoying... I just posted back to an
individual a message intended for the list
this is a repost to the list where I logically expected it to go, having
received it from the list.
> My grand plan, would let you create a complete XML base spec of data
> packaging, poll scheduling, publish timing, extraction etc so that I could
FTP
> the XML to the outpost device and it would do the right thing. I could
hand
> the same document to my broker and it would know how to extract the data,
and
> where to deliver it to...
Like I keep saying... why does it have to be XML? there is no real advantage
in this application. Should you want to interface XML for normalized
transport to *external* applications, conversion would be a fairly simple
task... so again, why must the "native" protocol use XML? What point to it
except wasting memory, speed and bandwidth?
XML is best suited for static storage and transport of data between
*dissimilar* applications/processes... in fact, that's what it was designed
for.
I feel fairly strongly that we need a far more efficient and small/fast
protocol, which XML is not.
- Brill Pappin
Rogue Robotics
www.roguerobotics.com
|
