Back to "DNS Problems now resolved - and on to some reflection stuff"

This is a viewer only at the moment see the article on how this works.

To update the preview hit Ctrl-Alt-R (or ⌘-Alt-R on Mac) or Enter to refresh. The Save icon lets you save the markdown file to disk

# DNS Problems now resolved - and on to some reflection stuff

<datetime class="hidden">2006-06-28T00:00</datetime>


## 
DNS Problems now resolved - and on to some reflection stuff

posted on Friday, August 20, 2004 3:22 PM

Well, seems my DNS provider uses some kind of procedure which can be prone to failure. Anyway, my DNS stuff is now functional again- yay! My plan for today is now to move on to playing a bit more with reflection and attributes...this could get interesting! Oh, in case you're wondering, I'm playing with the [Provider Pattern](http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspnet/html/asp04212004.asp) for a project I'm working on, also looking at doing some sort of low-maintainance security model for 'operational' security on method calls; so I can define that a particular method requires that my system provides the 'Edit' permission for that user / object before allowing the method call...probably going to involve extending the Provider Pattern to allow for permission attribute introspection as part of the provider...may be interesting ![](smile3_8225DB8F.gif)

This is a preview from the server running through my markdig pipeline

Imported mostlylucidcouk

DNS Problems now resolved - and on to some reflection stuff

Wednesday, 28 June 2006

DNS Problems now resolved - and on to some reflection stuff

posted on Friday, August 20, 2004 3:22 PM

Well, seems my DNS provider uses some kind of procedure which can be prone to failure. Anyway, my DNS stuff is now functional again- yay! My plan for today is now to move on to playing a bit more with reflection and attributes...this could get interesting! Oh, in case you're wondering, I'm playing with the Provider Pattern for a project I'm working on, also looking at doing some sort of low-maintainance security model for 'operational' security on method calls; so I can define that a particular method requires that my system provides the 'Edit' permission for that user / object before allowing the method call...probably going to involve extending the Provider Pattern to allow for permission attribute introspection as part of the provider...may be interesting