The "Behind-the-scenes" of SQUASH's Authentication
Yesterday we looked at how to setup a login form and process the information with ColdBox. Today we'll go a step further by viewing the code behind the authentication model.
Yesterday we looked at how to setup a login form and process the information with ColdBox. Today we'll go a step further by viewing the code behind the authentication model.
Now that we know what we're working with, we're going to need to sit down and understand how our users will be defined and how they will authenticate with the system.
Surprise! Yeah, I bet you didn't see that one coming, did you? It's Friday and I didn't want to start getting into the code just before a week-end. What better opportunity, then, to go ahead and announce the details of my new project? For your reading pleasure, I give to you: SQUASH.
So what does Coldspring do, anyways? We know by now that it's an Inversion of Control (IoC) framework. We also know that it helps us manage dependencies between objets. And yet, we're not quite sure what that means exactly yet. To help demonstrate the power of Coldspring, I've prepared a simple example.
Now that our application is setup, we want to make sure that it works. We'll start out by removing extra files we won't need. Once that's done we'll setup our default event and make sure everything's working.
Today I stumbled upon a strange lsDateFormat issue. On a project I'm currently working on (not THE project ;)) dates are stored in this format: "mm/dd/yyyy". Today, one of the pages started throwing an odd error:
Last week we were talking about using ColdBox and Coldspring to run our project. Let's take a look at how we actually make this happen.
Moving on with basic ColdFusion topics, today we'll look into the different variable types available. We'll also talk about the different ways of controlling the flow of the page through the use of conditional blocks and loops.
We now make it to the pièce-de-resistance. The next 2 or 3 posts should go over the basics of ColdFusion.
Earlier today I blogged about being aware of the differences between the way ColdBox and ColdFusion 8 handle variable names when serializing to JSON for remote calls (the original post name is much more elegant, I promise). Several questions arose as to the different ways variables can be created and how exactly each method would output, so I decided to put together this short test.