Re: Fwd: [Framework-Team] Re: PLIP 177 - Content indexing

2006-12-11 Thread Sidnei da Silva

On 12/11/06, Wichert Akkerman <[EMAIL PROTECTED]> wrote:

Previously Sidnei da Silva wrote:
> So we need to fix that. We can surely provide a 'stream' adapter for
> FileField. We should be able to change the transform API to make use
> of streams.

For 3.5 I'ld love to see a whole new transform infrastructure :)


I would be happy enough just to see something that works. New not
always equates to better. Old and beaten tends to be more robust.

--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: Fwd: [Framework-Team] Re: PLIP 177 - Content indexing

2006-12-11 Thread Wichert Akkerman
Previously Sidnei da Silva wrote:
> So we need to fix that. We can surely provide a 'stream' adapter for
> FileField. We should be able to change the transform API to make use
> of streams.

For 3.5 I'ld love to see a whole new transform infrastructure :)

Wichert.

-- 
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: Fwd: [Framework-Team] Re: PLIP 177 - Content indexing

2006-12-11 Thread Sidnei da Silva

On 12/11/06, Kapil Thangavelu <[EMAIL PROTECTED]> wrote:

> I am seriously concerned about the str(content) part. We have improved
> a lot the situation in other places in AT and it should not do that
> anywere else anymore (except in the transforms maybe). We need to
> fight that will all our forces. :)

the str(content) is basically arg marshalling for transforms, if you know
a way to pass a stream to the transform api... do tell. afaicr, internally
evening passing in an idatastream object using portaltranforms interfaces,
still assumes an accessor to a string blob.


So we need to fix that. We can surely provide a 'stream' adapter for
FileField. We should be able to change the transform API to make use
of streams.

--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: Fwd: [Framework-Team] Re: PLIP 177 - Content indexing

2006-12-11 Thread Kapil Thangavelu
On Mon, 11 Dec 2006 10:08:40 -0500, Sidnei da Silva  
<[EMAIL PROTECTED]> wrote:


-- Forwarded message --
From: Sidnei da Silva <[EMAIL PROTECTED]>
Date: Dec 11, 2006 11:58 AM
Subject: Re: [Framework-Team] Re: PLIP 177 - Content indexing
To: Rocky Burt <[EMAIL PROTECTED]>



Personally I think this plip would be awesome to get in place.  But with
one small stipulation.  I would adding a configlet someplace or some
config option somewhere that lets you toggle this behaviour on/off (on a
functional level) and have it off by default.  That way we don't have to
worry about the performance implications by default.  Then for Plone 3.5
we could consider having it activated by default.


I am seriously concerned about the str(content) part. We have improved
a lot the situation in other places in AT and it should not do that
anywere else anymore (except in the transforms maybe). We need to
fight that will all our forces. :)


the str(content) is basically arg marshalling for transforms, if you know  
a way to pass a stream to the transform api... do tell. afaicr, internally  
evening passing in an idatastream object using portaltranforms interfaces,  
still assumes an accessor to a string blob.


-k




___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team