Re: Frames, Transactions, and Elements

Hi John,

> But, within the realm of the SCE-MI world, let's at least
> use consistent terminology and something upward
> compatible with SCE-MI 1.

I agree that this is necessary or we're going to continue to
get lost in misunderstandings.

> Transaction:
>
> Element:
>
> Frame:
>

Actually, SCE-MI 1 used the terminology `message' for the unit
of data transferred in a single call.  I propose that use
message for what you proposed to call transaction, and transaction
for what you proposed to call frame.   Or alternatively, we can
reserve transaction for something defined by the user, VIP
implementor, application, e.g.:

  Message: Unit of data transferred in a single DPI call,
    SCE-MI 1 Send(), SCE-MI 1 receive callback

  Element: Same definition as yours

  Frame: A series of messages with the last message marked
    EOM (which should then be named End Of Frame, perhaps).

  Transaction: Exact definition depends on the transactor,
    i.e., it is up to the transactor designer/implementor
    to define how transactions are delineated.

Per

-- 
Per Bojsen                                Email: <bojsen@zaiqtech.com>
Zaiq Technologies, Inc.                   WWW:   http://www.zaiqtech.com
78 Dragon Ct.                             Tel:   781 721 8229
Woburn, MA 01801                          Fax:   781 932 7488