On fredag, augusti 9, 2002, at 01:42 , [EMAIL PROTECTED] wrote:
> Arthur's question towards transaction support would be the real, big > solution. > It would be really cool to support transactions, and if you have full > control > about the input that goes into components you can do rollback, make > snapshots, > all these fine things (and it is transparent to the component! :). > But I doubt that this is really needed and that we have the time to > code that. > You said (or at least I read it this way, correct me if I'm wrong) that > POE > apps should be small or mid-sized. There is overhead if you want to > support > transactions (using them could need less work). > On the other hand, if we can control the component's input, and if it > doesn't > do anything hidden or not repeatable, implementing it shouldn't be that > much > work (depends on the kind of distributedness). Granularity would be on > the > component level, performance could suffer from this. It could be on > component > attribute level if usage of accessors is enforced. > Anyway, the question is if people will want this or if it is easier for > them > to use protocols that avoid the need for transactions, atomic > operations, > and the like. > > I agree, transactions are often overkill and can be heavy, designing in support for transactions that can be enabled and added in the future would be very cool. We have all the time in the world :-) Arthur
