On Oct 24, 2007, at 07:09, bharder wrote:
> There are 3 ways (roughly) that I can think of
approaching this:
>
> 1) Complete integration, where this is deeply-tied into
Bric... I
> think this actually _not_ the route to go at all, as
it's blurring
> of the data-mangling that Bric does behind the scenes,
and front-
> end production _serving_, which Bric doesn't directly
deal with.
Agreed.
> 2) "Wrapping" a solution around Bric output
-- this is what Allan
> did when he wrapped the Bric output in Drupal
processing. The
> problem with this is
> a) performance
> b) dealing with multiple paradigms dealing with data
I'm not sure I follow you here. To my mind the ideal is
using
Bricolage for the back office workflow and publishing, and
to publish
it to a front-end like Drupal.
> 3) Co-processing -- (the route in using) is something
that sits
> "along side" the production server, and does
it's processing,
> feeding back to Bric. In this case Bricolage is still
quite
> seperate from the actual serving of content (as it
should be, in my
> opinion), but the results of the comments/forums are
fed back to
> Bric for integration on next publish. In my
imagination, this allows
> a) High performance
> b) Better seperation of the front-end/back-end
processing
> c) Even better integration than a "wrapper"
method
I never really did see the advantage of this. Why would you
want
forum data pushed back into Bricolage?
Best,
David
|