I am planning to utilize SharePoint lists in a custom solution. I would like content managers to make updates to the lists, and then publish the changes.

The lists would be accessed from DAL which creates DAL objects from list rows. DAL is referenced by BLL which is referenced by WCF which exposes the BLL objects through an IRepository to clients via REST and SOAP.

When content managers want to update values in the lists they just make the updates and publish the changes with a simple custom publishing feature which refreshes the cache with fresh data from the lists.

I would like to hear if ready-made solutions exist for this, whether I can reuse some existing APIs for caching lists (SP APIs?). How to refresh cache on all the front-ends?

  • What "cache" on WFE did you specifically have in mind? Some OOTB SharePoint caching, or perhaps something totally custom? How are you accessing the items that are "cached" on the WFE? – Jussi Palo Feb 5 '12 at 19:34
  • I am talking about totally custom caching. I would incorporate SharePoint list access in DAL, and deliver cached custom BLL objects to clients via WCF. (Users could perhaps have the possibility to publish changes via a simple SharePoint publishing feature which does refresh the cache.) – thomius Feb 12 '12 at 11:03
  • rewrote the question – thomius Feb 12 '12 at 11:28

Sounds a lot like the Patterns and Practices Entity Framework to me...

Also have a look at this: Simple data access pattern for SharePoint lists

And this: MSDN: The Repository Pattern

  • Thanks. Ended up making a repository which creates BLLs both from from sql (from oob sql entity framework) and sp (with additional layers for easy and fast access). – thomius Feb 21 '12 at 7:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.