Johan Björnfot
Feb 3, 2011
  4078
(2 votes)

Criterion implementation patterns

To implement a criterion to be used with the personalization concept introduced in CMS6R2 is pretty straightforward. There are however some guidelines to be aware of:

  • If you implement ICriterion.Subscribe and in the method set up an event handler for any event then you should implement ICriterion.Unsubscribe as well and in that implementation remove all event handlers that where setup in Subscribe.

The reason for this is to avoid getting “dangling” event handlers which cause both unwanted behavior (in meaning event handlers for unused/old criterions are still called) and “memory leakage” (old criteria instances cannot be garbage collected since they are rooted through the event handler).

The pattern for Subscribe/Unsubscribe is that Subscribe on each used criterion instance is not only called during initialization but also whenever a VisitorGroup containing the criterion is saved. During Save of a VisitorGroup the framework will first call Unsubscribe for all previous existing criteria's on that group. Then new criteria instances will be created for the group and Subscribe will be called on these instances.

 

  • Remember that IsMatch can be called several time during a request.

An obvious consequence of this is that the execution time for the call to IsMatch will affect the time for the web request. You should also avoid taking locks (or at least keep the scope to a minimum) inside the method since that would prevent requests from running in parallel.

If your criteria is dependent on some external resource (for example an external database) then you should take the scenario where the external resource is not accessible into consideration.

The purpose of this post is of course not to scare you from writing your own criteria's (that is something we encourage you to do) but to give you a guideline to successful criterion implementations! :-)

Feb 03, 2011

Comments

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog