[
Lists Home |
Date Index |
Thread Index
]
> Yesterday Len and Peter outlined two strategies. I would like to flesh out
> their ideas. ....... Imagine that a large system requires an Invoice
> XML vocabulary for a Book purchase.
> What do you (xml-dev'ers) think about all this? Can you think of other
> approaches? /Roger
Interesting application..
In a truly large scale system, like an industrial city, you
would have tens of thousands of open connections organised
into some sort grid arrangement.
What we tend to do now is insist on one connection per machine at the
client side and many connections at the server side.
It's purely historical.. been there many times. The manager
of the IT department says "We will have thousands of connections
(to our clients) - but they will only have one to us".
So everybody keeps writing what the boss of in the big
company wants.. not what is technically possible or what
is really needed.
There are tens of thousands of small/medium sized enterprises
that eagerly await software to break ranks and have this
multi-to-multi communication capability.
but reorganising the internet so that it can achieve it's next
degree of interoperation is something that can't be controlled by
governments or academic institutions.
I remember I suggested one time on this list that xml move
to version 2 and was told I couldn't contribute because I
wasn't in the W3C. Then surprise, xml moved to 1.1.
Goes to show.. some ideas work because they are forced... some
work simply because it is their time.
DL - crackpots anonymous
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
|
