Re: do we need plone.app.customerize? was: [Plone-Users] Insufficient privileges on folder_contents

Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <CANyGbvdQjjOGDAqqkYw5R6zfZAy7w7SHfCwQxHvChOAuVSef+w@mail.gmail.com>
On 13 Dec 2013 02:54, "Lennart Regebro" <[email protected]> wrote:
>
> On Thu, Dec 12, 2013 at 4:21 PM, Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]> wrote:
> > On the other hand ZODB gives you
> > - instant replication over many servers.
>
> You are on one hand claiming that TTW is needed because the standard
> egg-based way of doing things is too complex, and on other other hand
> talking about ZODB replication. That doesn't exactly match. ;-) In any
> case, replicating a file system is much easier than replicating a
> ZODB.

The person who runs the zeo cluster doesn't have to be the one who writes
the code. A single cluster run by say a uni can support hundreds of site
develops writing code in isolation. You can't do that with fs based code.
That is why I called my talk cms-as-a-service out of the box.

>
> > - Transactional code updates.
>
> Verison control.
>
> > - Memory management of code (All FS code is loaded in RAM all the time.
A big problem when you're running hundreds of sites)
>
> So here again you are talking about how eggs are complicated, and at
> the same time talking about Python code that apparently is so huge
> they create a memory problem. Seriously, if you are able to manage a
> site that has so much TTW code that it saves you significant amounts
> of memory compared to having it on the disk, then you are able to
> learn how to run a buildout.

I'd contend even if the same person is both developing and running the
site, skills required to install and run zeo is way less than those
required customize plone.

>
> > - instant code reload
>
> That's definitely a bonus.
>
> > We put all our TTW code in source control. We're trying to make it
easier with the development of plone.gitpush
> > https://github.com/collective/plone.gitpush
>
> Well, that's already a step forward, away from the traditional TTW model.

We aren't talking about how ttw is done now but what we need in the future
to replace skins and portal_customerize. I don't think we disagree that
replicated instant reloadable replicated secure isolated code important so
perhaps we should go back to talking about what that code should look like.

> //Lennart

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.