DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 620 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

5
kicks
submitted by jeremyjarrell jeremyjarrell 7 months, 11 days ago

jeremyjarrell.com — A brief discussion of how to implement the Monostate pattern, and what advantages it gives us over the Singleton pattern.

Add a comment 1 comment | category: | Views: 10 | Get KickIt image code
tags: | tag it

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:

Comments:
Ah, so I 'm actually doing monostate?
Seriously, I always thought Singleton is keeping an single instance of some object. As long as you implement all relevant ops as instance members of said object and give some entry point into your singleton keeper you're still well on your way for testability and all OO glory.
posted by fquednau fquednau 7 months, 2 days ago



information Login or create an account to comment on this story
 

Sponsored Link: www.carlist.ie

Search:

Ads via The Lounge