Avoid performance problems caused by MCMS Publishing API

re: Avoid performance problems caused by MCMS Publishing API

Jim — Tue, 16 Aug 2005 14:26:33 GMT

What if someone uses a > or a < in the placeholder?

re: Avoid performance problems caused by MCMS Publishing API

Stefan_Gossner — Tue, 16 Aug 2005 20:41:10 GMT

> and < as characters have to be stored as < or > otherwise the content is not valid html.

re: Avoid performance problems caused by MCMS Publishing API

Tobias — Wed, 12 Oct 2005 17:13:49 GMT

What about the PlaceholderCollection? Does it suffer from the same implementation as the CustomPropertyCollection?

re: Avoid performance problems caused by MCMS Publishing API

Stefan_Gossner — Wed, 12 Oct 2005 17:36:46 GMT

Yes it would. But I have never seen code that accesses placeholders this way.

re: Avoid performance problems caused by MCMS Publishing API

Nicholas del Rosario — Wed, 22 Aug 2007 04:01:37 GMT

Would accessing the bound placeholder rawcontent of an HTML or XML placeholder cause the same performance issues as the text property of the HTML placeholder?

re: Avoid performance problems caused by MCMS Publishing API

Stefan_Gossner — Wed, 22 Aug 2007 08:46:45 GMT

First of all: the problem with the Text property is solved with MCMS 2002 SP2.

Second: you should avoid DataSource.RawContent.

See here for details: http://blogs.technet.com/stefan_gossner/archive/2004/04/24/119546.aspx

To answer your question: no this will not have a performance problem.

re: Avoid performance problems caused by MCMS Publishing API

Nicholas del Rosario — Wed, 22 Aug 2007 12:11:34 GMT

Thanks, were encountering a minor memory leak in our environment, we did implement accessing properties without knowing if it exists, could this be a possible cause to a memory leak? Were still using SP1a for MCMS

re: Avoid performance problems caused by MCMS Publishing API

Stefan_Gossner — Wed, 22 Aug 2007 19:30:38 GMT

Support for SP1a has ended January this year. All server need to be on SP2 to be in a supported state.

To answer your question: no this will not lead to a memory leak.