Jon,
you actually gave me a very useful insight to
Turbine's way of doing things. But do you put ALL you
of your business objs in context?
I mean, say I request:
www.xxx.com/aaa/bbb/page1.vm
which needs the People business obj, and
www.xxx.com/aaa/bbb/page2.vm
which needs the Beers business obj.
Do I put People and Beers in EVERY request? page2
won't use People and page1 won't use Beers. This is no
big deal for 2 business objects, but what about 2000?
Maybe it's still acceptable, I don't know, this is
totally new to me.
This is also a question to Geir, because if I
logically partition an app into sections, it seems to
me that :
1.how do I do the partitioning without modifying the
controller every time? Say the designer wants busin
obj x on page/section y. I have to go into the servlet
and add it (regression test, and evils like that)? or
does the servlet look it up in a property file? or how
?
2.the granularity of this partitioning is too large,
and I still end up with tons of bus objs for a given
section in context that I don't need. It seeems to me
that the controller should know that page y needs
exactly busin objs x, k, and z. Or maybe I still don't
grasp the concept.
thanks for enlightening a layman like me. I will also
throw a party when I really learn Java programming.
piero
> example, I would have an object that looks like the
> one below placed into
> the Request context:
>
> public class RequestContextPullObject
> {
> private People people = null;
>
....
> Now, this object would be made available in the
> Context for each request as
> a $requestPull through the configuration of
> Turbine's Pull Service:
>
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
