Home > Blogs > Blog Post

To Interface or not to interface? Here is the question

by Hugo Esperanca | Dec 07, 2004

Isn't it funny that, suddenly, interfaces do not seem to be in fashion in the .Net world anymore ?

In the not so good old days of COM there wasn't an option - if we wanted a component we had to have at least one interface. The abstract server pattern was alive and kicking and the advantages of separating a service contract from its implementation were clear to all (at least to the ones using OO languages). In those days there was a clear distinction between a component (something providing services trough an interface) and a class.

Now, in the new world of .NET, we can have classes, in different assemblies, talking directly to each other. Call me an old fashion geezer but I still strongly believe in patterns like the Separated Interface and Factory (from one of my favourite books Agile Software Development). Perhaps I should go back to my perforated cards...

Compliance using DocRead

DocRead logoDocRead for SharePoint can help you manage policy compliance by:

  • Targeting documents or policies at specific groups of users
  • Allowing a specific amount of time for users to confirm agreement 
  • Sending email reminders when policy compliance is overdue
  • Users self-certify that they have read and fully understood the policy details
  • Securely storing records of confirmed policy acceptance
  • Monitoring the user acceptance of policies via a reporting suite
  • Providing detailed reading reports and statistics
  • Report drill through to show who has not accepted the policy
  • Automatically sending historic compliance tasks and policies to new users when they are added to a group
  • Bringing policy compliance requests immediately to users attention when they log on

DocRead is simple to install and configure. It seamlessly integrates with SharePoint and can be added to any existing SharePoint site.

To find out more, visit the DocRead product site.


blog comments powered by Disqus