cumulative summary page

cumulative summary page

Post by YmlsbCB0aW » Tue, 07 Sep 2004 20:51:01



We have authors who will contribute content to their respective channels.

One channel will hold a cumulative summary of all the postings in all
channels.

Questions:

1. Wouldn't it be better, and is it feasible, to have authors contribute to
ONE hidden channel out of which other channels can suck relevant postings?

2. If we take the classic approach, what is the most "elegant" and efficient
way to construct the cumulative summary ordered by date?
 
 
 

cumulative summary page

Post by Stefan [MS » Tue, 07 Sep 2004 21:13:09

Hi Bill,

the approach below seems to imply that one channel will hold more than 300
items.
Be aware that you will experience significant performance impact when more
than 300 items are stored in a single channel.

In addition: why are you creating summary postings rather than creating the
summary on the fly using server controls?

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://www.yqcomputer.com/ +2002+-+(complete)+FAQ.htm
MCMS Blog: http://www.yqcomputer.com/
MCMS Sample Code:
http://www.yqcomputer.com/ +Management+Server
MCMS Whitepapers and other docs:
http://www.yqcomputer.com/
--------------------------------




to
efficient

 
 
 

cumulative summary page

Post by Stefan [MS » Tue, 07 Sep 2004 21:13:09

Hi Bill,

the approach below seems to imply that one channel will hold more than 300
items.
Be aware that you will experience significant performance impact when more
than 300 items are stored in a single channel.

In addition: why are you creating summary postings rather than creating the
summary on the fly using server controls?

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://www.yqcomputer.com/ +2002+-+(complete)+FAQ.htm
MCMS Blog: http://www.yqcomputer.com/
MCMS Sample Code:
http://www.yqcomputer.com/ +Management+Server
MCMS Whitepapers and other docs:
http://www.yqcomputer.com/
--------------------------------




to
efficient
 
 
 

cumulative summary page

Post by YmlsbCB0aW » Tue, 07 Sep 2004 21:49:08


1.

Point taken, Stefan. Nonetheless, what do we do if we have more than 300
items? In fact, we already do in one channel.

2.

Hmm, have I said so? Right now, we're emulating the summary control found
in Woodgrove.

Still, Channel A (perhaps the home page) will show the summary of postings
in Channels B, C, D. The summary needs to be ordered by date. Hence, I
think the postings will have to merged. What's the best way of doing it?
 
 
 

cumulative summary page

Post by Stefan [MS » Tue, 07 Sep 2004 21:57:27

Hi Bill,

then you should create a tree structure below that channel to ensure that no
channel has more than 300 direct childs.
To merge posting collection use the Union method of the posting collection.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://www.yqcomputer.com/ +2002+-+(complete)+FAQ.htm
MCMS Blog: http://www.yqcomputer.com/
MCMS Sample Code:
http://www.yqcomputer.com/ +Management+Server
MCMS Whitepapers and other docs:
http://www.yqcomputer.com/
--------------------------------




more than 300 items are stored in a single channel.