Re: One Login EOModel for multiple apps?
Re: One Login EOModel for multiple apps?
- Subject: Re: One Login EOModel for multiple apps?
- From: Giorgio Valoti <email@hidden>
- Date: Tue, 8 Jul 2003 16:33:41 +0200
On Martedl, lug 8, 2003, at 15:53 Europe/Rome, james o wrote:
i would like to build a Login application that handles all logins for
multiple applications. all current applications will be built using
the same database server(OpenBase). i haven't worked with multiple
EOModels in one app so i have a couple questions.
-in EOModeler, how do i make relationships from the new Login Database
to my other EOModels?
-from what i've read in the lists, EOF handles all of the new to-one
and to-many relationships. is this true? any gotchas?
-does EOF lock the login object from any app referencing the Login
table? can the other apps referencing this object see that it's
locked? it seems like locking could get very complicated if two
people are editing the same object concurrently.
does anyone have recommendations or an example of how to use multiple
EOModel files before i get started?
Well, IMHO, there are several details to get right in your project:
- Multiple models, either within the application project or from
several frameworks should just work provided that you have unique
entity names. Usually, this is not an issue, but once you begin to use
pretty common entitity names like User, Login, Group and so on, you
should plan to use a prefix.
- It's not clear to me what you mean when you say 'EOF handles all of
the new to-one and to-many relationships'. In any case, say that you
have a framework with your authentication logic, the only way to
establish a relationship *from* this framework to other models is by
creating them at run time. You can do this in your application
constructor, either directly or with a principal class in the
authentication framework.
- You can have locking issues, but I think it's better to treat the
authentication framework as read-only from the application perspective.
There are also other subtle and not so subtle issues with this design;
in my spare time, I'm writing a framework that provides this kind of
functionality (and authorization for D2W apps), coupled with the
security framework written by Dave Neumann (thanks Dave!), I'll release
a preview to anyone is interested, between some time...
HTH
--
Giorgio Valoti
-------------
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.