on 11/21/2000 3:58 AM, "Raphael Luta" <[EMAIL PROTECTED]>
wrote:
> There's no "glue" between Jetspeed and Turbine.
> In this implementation, nearly everything we use in Jetspeed builds on top of
> Turbine: services, resources, modules, etc...
> Why only mark the modules as part of Turbine and not the services ?
> The choice for this implementation of Jetspeed is to use the Turbine
> framework, I
> don't see a real reason for "ghettoing" Turbine based code in a sub-package.
> We're advertised as a Turbine webapp so I think we should stick to existing
> Turbine conventions when they exist and I think we must have a very good
> reason
> to break these.
I agree. -1 on glue.
-jon
--
twice of not very much is still a lot more than not very much
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
