Magick Source

For some time now I started thinking that it was a good ideia to implement a pluggable authentication system on the MFWork.

Now, for a (at this time) close project (http://beakleakr.com) I really need to implement Facebook connect/login, so maybe this was a good time to implement that pluggable authentication system on the MFWork.

I will not do it yet on the MFWork, and will implement if on the closed project instead. And I have two reason for that.

1. At this time the things I will be connecting to the facebook profile are not relevant in other contexts - I will allow users to select their favorite leakrs, and send to their facebook wall the updates on those leakrs. I'll not implement at this time handler calls or anyother way to extend what I'll now do outside of the closed application.
2. This is the first time I try something like this, and I'm not sure what I'll really need, and I prefer to rewrite completly a small part of my closed source application than rewrite a major pluggable core part of the application - when I implement this into the applicaton, this must allow users to connect their authentication systems with the core authentication from the MFWork, and allow them to configure actions that they want to propagate to each of the systems they are connected with.

So, this implementation of facebook connect will allow me to understand how this works and what I will need to implement in the MFWork for future projects that use this kind of authentication and social interfaces.

And in a few month, a major changeset in the Mason FrameWork may include an implementation of remote authentication and publishing.

Just published [[NTP64bits2UnixTime|Convert NTP 64 bits time to UnixTime]], a small recipe that explains how to convert 64 bits NTP timestamps to Unix Timestamps.

the Mason Framework is now using jQuery for ajax and jQueryUI for the backoffice. This must be completly transparent for applications using the MFWork ajax handlers.