[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Re: UU: User state
In ideal case, C++ should not worry about implementation details ..
2006/9/13, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:
Of course it's going to be in database. I'm wondering about C++
side of things. Although I'm leaning towards having it in there as well.
Alexey Parshin wrote:
> A linking (proxy) object makes more sense to me. It's easy to
> implement and handle it within database.
>
> 2006/9/13, Ilya A. Volynets-Evenbakh <
ilya@total-knowledge.com
> <mailto:ilya@total-knowledge.com>>:
>
> OK. I need thoughts on this subject.
> User within UU has certain state in relation to each object he is
> working on.
> For example:
>
> Student is solving a problem. Student is reading topic explanations.
> Course author is writing something.
>
> There are two ways to organize this in our data model:
> 1. Make model classes directly include this information. Thus we
> will create
> A separate object for each user as they appear.
> 2. Organize things in a manner that's closer to what is in database:
> There is a user object. There is a content object. Then there is a
> linking
> object that binds them, and keeps user's state.
>
> Any pros and cons to each of approaches any of you sees?
> Any other ways to organize this?
>
> --
> Ilya A. Volynets-Evenbakh
> Total Knowledge. CTO
> http://www.total-knowledge.com
<http://www.total-knowledge.com>
>
>
>
>
> --
> Alexey Parshin,
> http://www.sptk.net
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
--
Alexey Parshin,
http://www.sptk.net