From: | Matthew Waddilove <m_waddilove@*******.COM> |
---|---|
Subject: | Re: FAB Revisited [was: Re: Chunk Launcher v.2.0] |
Date: | Sat, 16 May 1998 01:23:07 PDT |
>Wow. A -Workable- solution to the FAB net problem. Now if someone
>could make a decent explanation for unidirectional datalines from
>Neo-A's Guide to Real Life.
I've never had a problen with unidirectional datalines because of the
high level of abstraction of the matrix. Let me explain, now are you
sitting comfortably...
Unidirectional datalines are a matrix construct and hence only effect
'visible data' (datapackets, deckers, IC) this has to happen because if
it didn't Unidirectional datalines would be invisible from the send end.
What happens is the visible data goes in to the uni'line and the decker
standing at the end of the uni'line still recieves the Matrix protocol
messages that provide sight hence the dataline is'nt _Really_
unidirectional so there's no problem with a decker going down the
dataline as the control signals and the persona data can still pass
freely between the decker and deck.
This is also how I see Tracer IC tracking a decker. The IC reads the
Matrix protocol data and tracks that back to the decker. the Tracer
still could'nt track the decker trough a Uni'line as the IC's visible
form could'nt go down the dataline.
Hope this Helps.
-Matthew Waddilove
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com