xml-dev - Re: what Napster means for XML

["W. E. Perry" <wperry@fiduciary.com>]

Since you and I seem to be in reasonable agreement on the merits of the
distributed model for publishing, let's now consider the unique advantages of
the distributed architecture for dissemination of data beyond serving up simple
replicants. XML-ized network nodes are supposed to provide processing. In the
network and business architecture which I envision, the expertise of the human
at each node will be offered (for sale, or for free) as a value-added
transformation of data available elsewhere, but here assembled in unique
combination and processed in unique ways. The question is not then which of
several alternate sources to try retrieving some standard bit of data from, but
rather which specific node to approach as the place to find the data processed
and presented in the most usable form for our own purposes.

David Megginson wrote:

> Basically, a peer-to-peer system can make high-demand items available
> more easily by spreading the cost of distribution among more users,
> while a client-server system can make all items available predictably
> and in an easily-referenced location.  Look at the kind of information
> you're publishing, and make the choice.


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************