Friday 01 August 2008 11:17:48 pm
I'm not sure there is a best practice for that, or at least I'm not aware of it. Creating an object per comment and reflecting threads by structuring parent/child comments would be the default way, I think, and definitely some API exists to import that quite easily. But if you have a substantial number of those comments (going into tens or hundreds of thousands and above) and/or those comments are a key functionality and are expected to be very popular, then moving them into eZ Publish as objects may be risky - you'll end up with gigantic structure of objects of little singular importance. I such case I would think of moving this functionality outside of eZ Publish content model, into my own extension/database tables. But it would be really great to hear someone who has actually dealt with this problem!
Cheers, Piotrek
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|