Well, it is done. I zipped up my current version and have released it to the masses. If you are interested in checking out the new version, you can point a browser to http://whosoncfcdb.riaforge.org and check it out.

A few things are worth mentioning to help get you up and running if you would like to use it. I did not include the latest version of Transfer ORM in the distribution package. If you do not already have Transfer up and running your can get the newest version at http://www.transfer-orm.com.

All the Transfer related XML configurations as well as the MSSQL SQL generation script can be found in the /config folder. You will need to modify the datasource.xml file to the ColdFusion data source you will be using. Use the supplied whosoncfcdb.sql to generate your tables for you. As mentioned before, I do not have scripts for other database servers so if someone comes up with one for MySQL or another server please let me know. The data structure is simple and you should be able to look at the transfer.xml file and piece it together.

If there are any questions you can post them here and I will do my best to get them sorted out as quickly as possible.

I went ahead and submitted WhosOnCFCDB to RIAForge this morning. I was thinking it may take a little bit of time to get it approved since Ray lives next door to me, more or less, but apprarently it is hard to keep him down, hurricane or no.

WhosOnCFCDB is currently at version 0.9 which is a retooled version of WhosOnCFC 2.2.2 using Transfer ORM to handle storing user information as opposed to storing everything in an instanced component. This will make it easier for those of you who have WhosOnCFCDB running on multiple web sites and should allow you to monitor everything from once central location.

WhosOnCFCDB requires Transfer ORM 1.1 RC1 or above, any version prior to that you may encounter some problems.

As soon as I get things finished this afternoon I will upload it to RIAForge. It should be noted that this is a beta release so the documentation is sparse. I only have the SQL scripts for MSSQL server, any other SQL server will require some editing by hand, but the database structure is not very complicated.

Well, this is the third and final installment of my blog posts dealing with my crash-course in Transfer ORM. On the first day I roughed out my transfer.xml file that detailed my database structure and wrote the rudimentary functions that compose the gateway object WhosOnCFC uses to communicate with the database. On the second day I fleshed out some new functions that mimic the array functions in WhosOnCFC. Day three links the ActiveUsers table with a One-to-Many relationship to the PageHistory table which stores each page viewed by a session.

[More]

You can find the demo application here: http://amary.kisdigital.com

Well, instead of adding any additional tables to my transfer.xml, I decided to just finish adding the functions in the gateway object to make everything run as it should.

Everything seems to be running fine with the exception page loads are a little slow for my tastes. I will post the revised code for my gateway object and if anyone sees any obvious problems with it, any help would be appreciated. I decided to keep all the database interactions in Transfer as this was a learning experience.

[More]

I will preface this by saying the only Transfer experience I have thus far is installing it. Since that only required copying a folder onto the web server and adding a ColdFusion mapping, I am far from a Transfer expert and this will end up being a bit of a learning experience. I was going to put all the database interaction inside the WhosOn.cfc component, but after some consideration I thought it might be better to follow best practices and separate my service object from the gateway object.

[More]