Ok, I've been away for a bit doing abstract designs, and I see that I
leave this crew along for a week or two and they go off and redesign
_everything_ ;)
Coming back in, I find some curious and dearly inviting allusions to
techniques such as "Pipelines", with the only real hint being that
it has something to do with Tomcat 4 (I'm using tomcat 3.3, but I've
upgraded before ;)
My instinct says pipelines means cascading services, using the feed of
one service (say a database lookup) to feed another (say an XML rendering)
and having that feed another (XSLT transform to PDF) before returning
the page to the browser. Is this essentially correct?
I also found curious comments about improving binary and XML services,
which I hope implies exactly the reason why we were abandoning
Turbine.java for our site (we have no need of session management or
logins, we only need velocity, pools, caches, torque and just about
every other Turbine service ;)
I've tried to sift my backlog of mailing list messages, but found nothing
(absense of evidence is not evidence of absense) --- can someone point me
to any kind of archive/log/doc where I can learn more about what evil
world-domination plans you are hatching here with Turbine 3.0? Is there
a pill I can take so I will understand what I find? ;)
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
