FileSystemStorage vs blob

5 messages Options
Embed this post
Permalink
Kurt Bendl () FileSystemStorage vs blob
Reply Threaded More More options
Print post
Permalink
Thanks again for the buildout, Andreas!

It got me thinking about UofL's implementation. We're hooking File and
Image to use blob (http://plope.org/software/blob/) using BlobFile. We
were strongly encouraged to go the blob route by the Enfold folks who
we hired when we did our initial deployment about 2 1/2 years ago. It
was a bit odd working with the way it handles at first, but blob does
seems to work pretty well.

I'd really like to hear everyone's opinion on storages. We're
considering what it is going to take to migrate from 2.5.x to plone
3.0.x. How we're going to handle files is a big part of that.

/me sits back and awaits the volley


Best,
  Kurt

  Kurt Bendl
  University of Louisville

_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational
ajung () Re: FileSystemStorage vs blob
Reply Threaded More More options
Print post
Permalink


--On 21. Dezember 2007 14:53:15 -0500 Kurt Bendl <[hidden email]> wrote:

> Thanks again for the buildout, Andreas!
>
> It got me thinking about UofL's implementation. We're hooking File and
> Image to use blob (http://plope.org/software/blob/) using BlobFile. We
> were strongly encouraged to go the blob route by the Enfold folks who
> we hired when we did our initial deployment about 2 1/2 years ago. It
> was a bit odd working with the way it handles at first, but blob does
> seems to work pretty well.
>
> I'd really like to hear everyone's opinion on storages. We're
> considering what it is going to take to migrate from 2.5.x to plone
> 3.0.x. How we're going to handle files is a big part of that.
>
>
Nothing against blobs. Blobs are a pretty new ZODB technology and it is
nice to have them now in the next Zope 2.11 release. On the other hand FSS
has been a very strong and reliable products for years...so it is basically
risk-free (for me as a developer). In addition it provides RDF generation
for files on the FS and it is easy to deliver files  through Apache because
the file used contain the object's UID...pretty handy.

-aj

_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational

attachment0 (193 bytes) Download Attachment
Nate Aune () Re: FileSystemStorage vs blob
Reply Threaded More More options
Print post
Permalink
In reply to this post by Kurt Bendl
Hi Kurt,

I would recommend using plone.app.blob which is likely to land in
Plone 3.5 and be the default way of handling external files for the
ATFile content type. Andi Zeidler (cc'ed) has done a lot of work
recently to get this working. http://plone.org/products/plone.app.blob

If you want to try it out, the easiest way is to testdrive the buildout:

svn co http://svn.plone.org/svn/plone/plone.app.blob/buildouts/plone-3.0 blobs
    cd blobs
    python2.4 bootstrap.py
    ./bin/buildout
    ./bin/instance fg

There's also a very comprehensive howto written up here:
http://myriadicity.net/Sundry/PloneBlobs

Nate

On 12/21/07, Kurt Bendl <[hidden email]> wrote:

> Thanks again for the buildout, Andreas!
>
> It got me thinking about UofL's implementation. We're hooking File and
> Image to use blob (http://plope.org/software/blob/) using BlobFile. We
> were strongly encouraged to go the blob route by the Enfold folks who
> we hired when we did our initial deployment about 2 1/2 years ago. It
> was a bit odd working with the way it handles at first, but blob does
> seems to work pretty well.
>
> I'd really like to hear everyone's opinion on storages. We're
> considering what it is going to take to migrate from 2.5.x to plone
> 3.0.x. How we're going to handle files is a big part of that.
>
> /me sits back and awaits the volley
>
>
> Best,
>   Kurt
>
>   Kurt Bendl
>   University of Louisville
>
> _______________________________________________
> Educational mailing list
> [hidden email]
> http://lists.plone.org/mailman/listinfo/educational
>


--
Nate Aune - [hidden email]
company: http://jazkarta.com
blog: http://nateaune.com
twitter: http://twitter.com/natea

_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational
ajung () Re: FileSystemStorage vs blob
Reply Threaded More More options
Print post
Permalink


--On 22. Dezember 2007 14:16:20 -0600 Nate Aune <[hidden email]> wrote:

> Hi Kurt,
>
> I would recommend using plone.app.blob which is likely to land in
> Plone 3.5 and be the default way of handling external files for the
> ATFile content type. Andi Zeidler (cc'ed) has done a lot of work
> recently to get this working. http://plone.org/products/plone.app.blob
>

I would stick with the functionality that is available ouf-of-the-box.
That means this functionality is supported (and supported hopefully
when it comes to migrations). I would never consider such a configuration
for a production environment unless you like the risk and have the skills
to deal with upcoming problems and migration issues. This is a general good
rule and has nothing to do with the upcoming blob support.

Andreas

_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational

attachment0 (193 bytes) Download Attachment
Andreas Zeidler () Re: FileSystemStorage vs blob
Reply Threaded More More options
Print post
Permalink
On Dec 23, 2007, at 7:57 PM, Andreas Jung wrote:
> --On 22. Dezember 2007 14:16:20 -0600 Nate Aune <[hidden email]>  
> wrote:
>> Hi Kurt,

hi kurt :),

>> I would recommend using plone.app.blob which is likely to land in
>> Plone 3.5 and be the default way of handling external files for the
>> ATFile content type. Andi Zeidler (cc'ed) has done a lot of work
>> recently to get this working. http://plone.org/products/ 
>> plone.app.blob

while i'd appreciate you giving this a try and me some feedback, of  
course :), ...

> I would stick with the functionality that is available ouf-of-the-box.
> That means this functionality is supported (and supported hopefully
> when it comes to migrations). I would never consider such a  
> configuration for a production environment unless you like the risk  
> and have the skills
> to deal with upcoming problems and migration issues. This is a  
> general good rule and has nothing to do with the upcoming blob  
> support.

...i'd agree with andreas that you shouldn't use it in a production  
environment yet.  while it seems to work for some people and allows a  
content type based on zodb blobs to be used as a drop-in replacement  
for atcontenttype's "file" type (with all tests from cmfplone and  
atcontenttypes passing), it's still in an alpha state and generally  
not tested widely enough to be safely used in production.

having that said, let me point out that it doesn't use a special  
branch of zope anymore, plone 2.5 support is currently underway and  
probably there will be a migration path from FSS as well.

cheers,


andi

--
zeidler it consulting - http://zitc.de/ - [hidden email]
friedelstraße 31 - 12047 berlin - telefon +49 30 25563779
pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/
plone 3.0.4 released! -- http://plone.org/products/plone


_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational