Mirko Viviani wrote:
David Ayers <[EMAIL PROTECTED]> ha scritto:I must admit, if you really want to catch this case of:
In the very unlikely event that no messages get sent to EODatabaseContext before the the EOCooperatingObjectStoreNeeded Notification gets posted, we should just make sure to call some EODatabaseContext method (like [EODatabaseContext class]) real early to force the runtime to send +initialize to EODatabaseContext.The problem is really this... how to be sure that a message will be sent to
these classes ?
int main (int argc, char **argv)
{
EOCooperatingObjectStore *coopstore;
coopstore = [[NSNotificationCenter defaultCenter] postNotification: @"EOCooperatingObjectStoreNeeded"
object: nil]
}
then I'd have to pass this on to the real objc runtime experts.
But lets see what we can do...
The current implemetaion of _registerDatabaseContext: either needs some EOGlobalID, EOFetchSpecification or a customEntityObject. In the later case (customEntityObject) we can be pretty sure that EODatabaseContext has been initialized. So putting an [EODatabaseContext class] in the implemetatiin of +initialize of EOFetchSpecification and EOGlobalD would put us on the very safe side for any 'legal' notification.
The implementation of _registerDatabaseChannel: expects an EODatabaseContext in the notification, so we could add a [EODatabaseChannel class] to EODatabaseContext's implementation of +initialize.
I think this should be all the security we need.
Cheers,
Dave
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep
