todd scripsit:
> I would never advocate an API only approach because it requires a port
> of the API to the
> machine you are using and the language you are using. Not exactly a
> recipe for mass
> adoption. Using the protocol approach we can have the best of both worlds.
As someone who generally favors bits over API, I think the posterchild
for the API approach is the sockets API. I can scarcely imagine anyone
who would avoid this in favor of manipulating TCP, UDP, and IP bits
themselves. If there's no implementation of sockets (even a semi-broken
one like Winsock), network programming is a plain non-starter on that
platform until it's ported.
--
John Cowan <> http://www.reutershealth.com
I amar prestar aen, han mathon ne nen, http://www.ccil.org/~cowan
han mathon ne chae, a han noston ne 'wilith. --Galadriel, _LOTR:FOTR_
