Archive for category FaxIt Nice

Received Faxes Distribution Problem

Posted by declanshanaghy in FaxIt Nice on January 24th, 2008

Update 1/24/2008 4:22pm

Dear Members,

The distribution problem has been fixed, all corrupted faxes have been resent and the original charges to your account have been voided. We hope you had a productive day despite this upset.

Sincerely,
Declan Shanaghy
350 Nice Inc

Read the rest of this entry »

No Comments

SCM Heaven – Continuous Integration

Posted by declanshanaghy in FaxIt Nice on December 18th, 2007

With the small development team we have here in 350 Nice I always pretty much dismissed the advantages of running a continuous integration (CI) server. But every now and then a build does break, and it does affect people. This weekend i explored the magical world of CI. And i only scratched the surface i know that much.

Read the rest of this entry »

,

No Comments

Ghostscript problems

Posted by declanshanaghy in FaxIt Nice on December 10th, 2007

After installing JODConverter the other day i was feeling ecstatic about how we can now handle document conversion in FIN 3.0 . However upon first use i got hit with a brick in the face!

Read the rest of this entry »

No Comments

Office Document Conversion Revitalized

Posted by declanshanaghy in FaxIt Nice on December 6th, 2007

I just found a cool new document conversion library based on OpenOffice.org. As you may know OpenOffice.org is the foundation of our office document conversion system in FaxIt Nice. We’ve been using legacy OpenOffice.org 1.3 for a long time now. It’s reliable but dated. No support for WordPerfect and ODT. This new framework will allow us to upgrade to OpenOffice.org 2.3. Wahooooo!!

No Comments

FaxIt Nice 3.0 is on the way

Posted by declanshanaghy in FaxIt Nice on December 5th, 2007

FIN 3.0, as i like to call it, the latest version of FaxIt Nice built on the turbine webapp framework is getting closer to production every day. I just closed out 2 massive blocker bugs which were preventing session serialization between the cluster nodes.

Actually i had to workaround both of them. The first was a bug in the web framework (Turbine 2.3.1) Its default user object is not serializable which prevents serialization of the session over the multicast socket.

The second is a wierd one, and I don’t really like my workaround. Basically some session data is lost during session failover from a crashed node, so i have to maintain another piece of session data to rebuild the lost data. Its hokey but until i can find out why the data is being lost in the first place I’ll just have to live with it this way

Anyway, the number of bugs is steadily decreasing and soon I’ll have to start making my list and checking it twice.

No Comments