On Sun, 2002-05-05 at 17:27, Bill Holloway wrote: > Gulp. OK. That steepens the learning curve -- maybe -- I was wondering > what all the "Flux" stuff was. > > Are there any users of this "mixed" model out there who have an opinion on > its stability/usability? Thanks.
It's very useful, but each model has its place. Push model: I have a Java class tied to a particular screen (or layout), and the Java class pushes the data to that particular screen/layout. The data is available only to that particular screen. Good for special purpose applications, e.g. restricted-access admin functions. Pull model: I have a Java class that creates data that might be useful on any number of arbitrary pages, and I can include that data on any screen or layout I want. The nice thing about pull model is that you can define dynamic data, and make it available to less-technical designer types, without having to know or care which screen or template it appears on. For example, if you have a Localinfo pull service that defines a time(), date() and weather() method, you can tell your HTML pushers that they can easily include dynamic time, date, and weather info in their pages just by inserting tags that say $localinfo.time() $localinfo.date() $localinfo.weather() They can put that much on a 3x5 card, and then design the web site however they like. The difference between push and pull is strictly a matter of how the dynamic objects get put into the Velocity context. In the push model, a screen-specific or layout-specific class puts the dynamic object into the context for that particular screen/layout. In the pull model, the pull service put the dynamic object(s) into the Velocity context of all screens and layouts. In fact, the pull service puts the objects into the contexts of screens and layouts that have push-model objects, so if you have a screen that uses the push model, you can use both push and pull in the same screen. Caveat: I'm still learning Turbine, so if I'm misrepresenting something, feel free to correct me, but I believe that's correct. Mark Nutter [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
