Ted Leung wrote:
The first action item on the wiki page says cleaned up
notification API...
oh, duh, somehow I saw everything else but that :)
One question is do we really need a class or could we do with
module variables/functions? When you say persisting asynchronous
callbacks, do you mean persisting the subscriptions? Persisting the
actual callback code? Or persisting unconsumed notifications?
bleah, I meant subscribers/subscriptions, sorry.
and sure, a module works too.. I guess I was thinking you'd need it for
persistence, but there are probably ways around that.
Alec
Ted
Alec
Ted Leung wrote:
The action items that we agreed on at the collections
code/design review are here: <http://wiki.osafoundation.org/bin/view/Journal/
TedLeung20050912>
One of the items is to move away from use of onValueChanged and go
back to using constructors for creating various collection kinds.
Unfortunately, this
means that we wouldn't be able to use update to change existing
instances in the repository. So we can't remove the onValueChanged
stuff, so it doesn't
make sense to duplicate the code in the collection item constructors.
So I'm just going to leave the code the way that it is now.
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
----
Ted
Leung Open Source Applications Foundation (OSAF)
PGP
Fingerprint: 1003 7870 251F FA71 A59A CEE3 BEBA 2B87 F5FC 4B42
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
