You, O Best Beloved, are a Singleton. There is nobody else like you in the whole wide world, nor has there ever been. You’re a singular occurrence, a unique random combination of genetics that exists only wherever you happen to be at a given moment. And if any of your friends wants to interact with you, they know just where to find you. You can interact with lots of different people, but no matter how many friends you may have, every one of them is interacting with the exact same YOU. When your good friend Dave asks you to tell Theresa hello next time you see her, you store that information and next time you interact with Theresa, you pass along that exact message.
You getting the picture here? If you instantiate a CFC and put it in a place (Application scope, anyone?) where EVERY other part of your application is able to interact with THAT PARTICULAR instance of your CFC, then YOU, O Best Beloved, have created your object as a Singleton. Now, for whatever reason, people seem to be awfully fond of tossing around the buzz phrase “Singleton Pattern”…not sure why. It’s way simpler just to use the word as an adjective describing how you have instantiated your object, and it makes more sense, too.
- It’s vital to understand this term because it has a huge effect on how your app will work. Basically, if an object is created as a Singleton and you aren’t able to visualize what that means, you could have people seeing other people’s data. Not good.
POP QUIZ!
Which of the lines of code below is creating my object as a Singleton?
B) <cfset application.adminObject = createobject("component",model.admin) >
You are not logged in, so your subscription status for this entry is unknown. You can login or register here.
I wonder if you could supply the answer upside down on this page?
Now THAT would be a bit of CSS!
Come to think of it, I know that there's some sort of RIGHT-TO-LEFT CSS...
psenn,
I understood that phrase to mean "as far as I know" or "to the best of my knowledge"