[SAIL-Dev] Re: Problem with session backup persistence

[Aaron Unger]

OK. The changes are checked in. Let me know if suddenly OTrunk data isn't be saved, or too much is being saved. Also, see my comment below. Scott Cytacki wrote: ...snip... - Is there a way to detect whether a sock entry comes from the current sessionBundle (thus possibly avoiding the need to modify ISock)? You could add a way, by modifying the emf sock entry model to include a non-containment and non-persistent reference field which points to its sessionBundle. Then compare that to the current sessionBundle. It is probably easiest if we did that together if you want to do it. There is a pretty high learning curve on emf, but once you've done it a few times it makes sense. However, if there are no objections, the way you have done it is better because it isn't tied to the "ot.learner.data" name. It is basically the "hint" option I described and you are using the boolean argument to specify the hint. My thought on this was that if you could tell where it came from, the Sock.add() method could make the decision on whether or not a new sockEntry needs to be created when replace is "true". That would help simplify the code in the step itself a little bit. But for now, I'll leave it how it is. -- Aaron --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to SAIL-Dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---