info in kvp_frames and scheduled transactions

[Robert Graham Merkel]

Excuse me while I dump a pile of dead, smelly animals over the place, but
here goes . . .

While looking at the problem of "schedulising" transactions from actual
register transactions,
it's just occurred to me that there is a big blob of data that it's not
clear what we should
do with it.  The transaction and split kvp_frames, namely.

While for now I'll just do the safe thing and simply ignore kvp_frames,
what happens when 
we start using the kvp_frame info more heavily?  Is it going to be safe to
duplicate kvp_frame
info as a block to insert into instantiated transactions?  Are we going to
need hooks for
scheduled transactions to know how to deal with each key in a kvp_frame
when instantiating?

Is this as ugly as I think it is?


-- 
------------------------------------------------------------
Robert Merkel	                           rgmerk@mira.net

Go You Big Red Fire Engine
-- Unknown Audience Member at Adam Hills standup gig
------------------------------------------------------------