[ih] "how better protocols could solve those problems better"

John Day jeanjour at comcast.net
Thu Oct 1 07:27:57 PDT 2020


Actually, it isn’t so much the protocols as different (better defined, perhaps) object models or schemas that are needed.
 
The operations are pretty much the same.  You can cover most everything with create/delete, read/write, and start/stop and at worst send a script and start it.

The fundamental difference is that data transfer protocols modify the state internal to the protocol, 
while application protocols modify state external to the protocol.

It is much easier, faster, less error prone, etc. to modify 'object models’ than protocols.  Of course it is more fun to do new protocols.

Take care,
John




> On Oct 1, 2020, at 09:51, Miles Fidelman via Internet-history <internet-history at elists.isoc.org> wrote:
> 
> On 9/30/20 9:59 PM, John Gilmore via Internet-history wrote:
> 
>> Craig Partridge <craig at tereschau.net> wrote:
>>> * Naming and organizing big data.  We are generating big data in many areas
>>> faster than we can name it.  And by "name" I don't simply mean giving
>>> something a filename but creating an environment to find that name,
>>> including the right metadata, and storing the data in places folks can
>>> easily retrieve it.  You can probably through archiving into that too (when
>>> should data with this name be kept or discarded over time?).  What good are
>>> FTP, SCP, HTTPS, if you can't find or retrieve the data?
>> The Internet Archive has this problem.  I'm not the right expert to talk
>> about what they've done, but I can introduce you.
>> 
> For a long time, I've maintained that we need a new generation of application layer protocols, for things like:
> 
> - mailing list management (it's really a routing protocol,  isn't it?)
> 
> - distributed map-reduce (on beyond encoding search strings after the ? in URLs)
> 
> - distributed process management (in the cloud, an awful lot of o/s functions would seem better handled by protocols)
> 
> But we could start by actually fixing things like calendaring - where the protocols exist, but nobody seems to implement them well.
> 
> Miles Fidelman
> 
> -- 
> In theory, there is no difference between theory and practice.
> In practice, there is.  .... Yogi Berra
> 
> Theory is when you know everything but nothing works.
> Practice is when everything works but no one knows why.
> In our lab, theory and practice are combined:
> nothing works and no one knows why.  ... unknown
> 
> -- 
> Internet-history mailing list
> Internet-history at elists.isoc.org
> https://elists.isoc.org/mailman/listinfo/internet-history




More information about the Internet-history mailing list