(more...)]]> http://www.thamtech.com/blog/2008/04/25/gmail-to-google-apps-email-migration-part2/feed/ http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/ http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/#comments Sat, 29 Mar 2008 05:06:33 +0000 Tyler http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/ I came up with a method for migrating the emails in my personal Gmail (user@gmail.com) email account to my Google Apps (user@thamtech.com) email account. I had a few simple requirements:

• Every email in the @gmail.com account must be migrated into the @thamtech.com account with all attachments intact.
• The read/unread status of each email must be maintained.
• The labels applied to each email must be maintained, whether they were applied by a filter or manually.
  • Certain Google-endorsed migration solutions are only able to maintain message labels that were applied automatically by a filter.
• The starred/non-starred status of each email must be maintained.
• The date on migrated emails must be the original date, NOT the date of migration.
  • Certain migrations involving Entourage have had this unfortunate result.
• The Recipient column when viewing the list of migrated Sent Mail must show the recipients of the emails, NOT my name or "me".
  • Certain migrations involving involving Entourage or Outlook have had this unfortunate result.

Also, Gmail normally replaces my name with "me" when displaying the sender/receiver of emails. I prefer that the emails display exactly the same, "me," after being migrated, rather than saying "user@gmail.com". Is this too much to ask? No!

I found a solution using imapsync and Amazon EC2 (I suppose any old computer would do, but this gave me a much higher bandwidth connection to Google's servers than I would have had otherwise). Here's a brief overview of my procedure:

(more...)]]> http://www.thamtech.com/blog/2008/03/29/gmail-to-google-apps-email-migration/feed/ http://www.thamtech.com/blog/2007/11/07/consuming-webservices-with-complex-input-parameters/ http://www.thamtech.com/blog/2007/11/07/consuming-webservices-with-complex-input-parameters/#comments Wed, 07 Nov 2007 17:50:53 +0000 Tyler http://www.thamtech.com/blog/2007/11/07/consuming-webservices-with-complex-input-parameters/ ColdFusion sometimes has trouble assembling the inputs to a web service when the parameters to the web service function are complex. I ran into trouble recently when trying to use the findObjects() method of the API-A interface to a Fedora Commons repository.

There is a discussion of this issue in the adobe forums with a good description of ColdFusion's behavior when preparing parameters for a web service call.

I am really enjoying Agile Database Techniques. I plan to read it again and take notes before I have to return it to the library! I began reading the book before starting on my new project at work. Shortly after I realized we may be facing an integration (of some sort) with a legacy database, I got to chapter 8: Legacy Databases - Everything You Need to Know But Are Afraid to Deal With. It has been very helpful as I move forward in the planning stages with my co-workers.

Dreamhost offers "One-Click Installs" of various web applications, including the software now running this blog: WordPress. It's written in PHP.

I didn't have very many entries in my blog, so transferring things from the old one to the new one hasn't been very difficult. I have rules in my .htaccess file redirecting the old urls to the new ones.

On the old blog, I was using my own template, but now I'm just using the default WordPress template. Maybe I'll replace it with my own some day when I have more time.

In addition, you can invoke a function through Flash Remoting or as a Web Service.

I recently discovered that if you invoke a remote function through a URL or a form on a web page, the arguments are automatically URLDecoded for you before the function is invoked.

I had some input in a form that included a '+' character. The browser naturally encoded the '+' into '%2B' before posting to my component function, as it should. Then ColdFusion (behind the scenes) decoded the string back to '+' before calling my function.

The problem was that in my function, which I knew was being called from a form, I immediately called URLDecode() on my input, to convert any instances of '%xx' to the correct character. Well, a '+' represents a [space] in a URL-Encoded string, so the '+' that was in the original input ended up as a [space].

The moral of the story is to be aware that ColdFusion will automatically URLDecode arguments from the URL or form before invoking your remote component method being invoked directly.

The locations are divided up into categories (as provided by the professor). Clicking on a category on the left will bring up markers on the map corresponding to the locations in the category. Clicking a marker will identify the location in an info window/balloon. Clicking a particular location within a category will center the map on the marker for that particular location.

then instantiating an object of type Manager will have a salary property set to 70000, because the cfset runs in Employee first, and then in Manager.

This makes pretty good sense to me. The values of the child component override the values set in the parent.

This doesn't apply only to variables being set, though (whether it be the public this scope or the private variables scope). If you call a function from the initialization code of a parent component, the function is called as it exists in the parent - the child part of the object has not been instantiated yet.

So with the example components above, the call to init() from within the initialization code of the parent component, Employer, makes a reference to the otMult() function. Since the child part of the object has not been instantiated yet, the otMult() call returns 1.5, instead of the value of 2 you might want if you are instantiating a Manager.

If this becomes a problem for you, I suggest that you NOT try to call your initialization functions from the initialization code block of a component, and instead, put all your initialization code within init functions and call your init() function when you instantiate an object:

Happy Coding!