I got it working and ran it over night to be sure it was going to hold up. The code looks very, very much like the code for updating ThingSpeak, so there aren't too many surprises. Once again, this is a standalone process that takes items from a simple database and forwards them to emoncms for archival.
As usual, it's way over commented. I think there's a lot more lines of comment than lines of code in these things.
Now, I have only one more of these to build, the one to keep my legacy feeds at Xively up to date. I want to keep them running when I turn off the old controller so I can transfer the data from them to the new Xively interface. Then, I'm going to take a look at a new service that just came on line a little while back to see how they work.
Cloud services are the way of the future IMHO.