1996-06-23 - RE: info assembly line, “flits” (long)

Header Data

From: blanc <blancw@accessone.com>
To: “‘Vladimir Z. Nuri’” <vznuri@netcom.com>
Message Hash: d9f777e9d8eb6a0a36c85133f10ca1b867613ce85893dede4637bee93ee56bb2
Message ID: <01BB6068.3EA6BA80@blancw.accessone.com>
Reply To: N/A
UTC Datetime: 1996-06-23 05:35:47 UTC
Raw Date: Sun, 23 Jun 1996 13:35:47 +0800

Raw message

From: blanc <blancw@accessone.com>
Date: Sun, 23 Jun 1996 13:35:47 +0800
To: "'Vladimir Z. Nuri'" <vznuri@netcom.com>
Subject: RE: info assembly line, "flits" (long)
Message-ID: <01BB6068.3EA6BA80@blancw.accessone.com>
MIME-Version: 1.0
Content-Type: text/plain


From: 	Vladimir Z. Nuri

"flits" would have an identity irrespective of companies. one
could track them moving through different companies if necessary.
(the "flits" might therefore also have security aspects associated with
them.)  the point is that the data must not be disconnected, it
must be seen as continuous, and I think a flit-like concept is key
to accomplishing this.
...................................................................


Wouldn't this accounting of "flits" require that each of them be assigned a tag?   

Since this would encompass all the "flits" in cyberspace irrespective of who/where used them, whose "flits" would be counted first, beginning where?   

And once one "flit" was attached to a document which was maintained as a permanent structure somewhere in someone's database, that means it could not be used anywhere else, and how would this work for copies made of that original document?  

Once a "flit" was used as a copy and then detached and re-associated with some other document several times, would each new copy carry a record of where it had been previously, so that half of the amount of space of a document would be comprised of the historical record of where that "flit" had been?

Sounds very costly.

     ..
Blanc





Thread