- As a service designer, you don't need to second guess every case that developers may come up with.
- As a developer and service consumer, you can construct a perfect single web service call, every time.
Friday, December 2, 2011
Wednesday, November 23, 2011
- The v0.0 and v1.0 API's were versioned, the v1.1 API is versioned and modular using SOA principles.
- FTPS and FTPES are now supported for first line storage as well as with CDN storage with Amazon S3 and more to come.
- Campaign members can now email media and have it ingested into ThumbWhere with their own email address or a pre-generated ThumbWhere specific email address.
- We have changes under the hood to improve the reporting of ingestion and transcoding workflow exceptions and new operations in the primary distributed workflow engine.
- Auto-generated windows tools . PowerShell 'Snap-ins' for each of the new services to allow easy scripting and tool writing. Windows workflow 'Activities' are on the way.
- Media can be FTPd directly to ThumbWhere on a per member or campaign basis.
- A lot of work has gone into making our internal development process more agile with a lot more code generation. Now we can design, generate and stand-up a new SOA service and supporting repositories in a matter of hours.
Sunday, August 22, 2010
Checked in SFTP support.
We need to test with more SFTP servers than we have in the development environment, but this is all ready for testing.
Now for FTPS and plain old FTP.
One side effect of the AmazonS3 Storage integration is that now every time we run automated my integration tests it costs us a few fractions of a cent. :)
But it is well worth it :)
Sunday, July 4, 2010
I just checked in the test candidate for external storage which supports Amazon S3 and FTP.
When this is deployed, API licensees can provide one or more Amazon S3 or FTP accounts and ThumbWhere will use that to store your media.
You specify an account and then a number of selectors which are used to select media for inclusion (or exclusion) with respect to a designated storage provider.
For example. You might want your videos stored in one S3 account and your thumbnails in another. In fact you might want to deploy certain thumbnails to a different type of storage altogether.
So by configuration of selectors and storage endpoints you can obtain a high degree of control over where your content is actually stored.
The system is architected to support generic storage providers via a plug-in model so I’m now investigating what others I can support in the first release. If I don’t see any easy wins then S3 and FTP will be the only ones in the first release.
I spent a good portion of Sunday writing automated tests to ensure that the core flow processor was able to handle the cases of first time deploy, revocation and update with the minimum amount of API calls and traffic. If multiple deploy instructions for the same media gets into the queue the engine is able to avoid double handling. If some of the media is modified and re-transcoded but all the media is marked for redeployment, only the media that has actually changed will be deployed.
You put a bit more thought into these things when you get a running bill from Amazon per API call and byte shipped. This weekends efforts added up to 3c :)
I’m also considering personalised storage, so actual end users of the system (members of each social network) could in theory provide their own S3 account info and have their own media shipped off to their own storage.
The media in external storage is represented by extra URL elements in the raw feed XML. The default XSLT for the account specific feeds will make this transparent by selecting a single URL and favouring external storage over files hosted on internal ThumbWhere storage.
We will start to factor this into our pricing model but the immediate effect is that this will allow you to ship most of your media traffic to cheaper storage and it will allow us to control our own storage costs.
Friday, July 2, 2010
Sunday, September 6, 2009
“MahTweets is a rich, awesome, twitter client, feature inline media, filtering, tracking (saved searches) and much more”
MahTweets can be downloaded from http://theleagueofpaul.com/mahtweets/
The ThumbWhere plugin was developed by @WillHughes
It supports Image uploading and uses ThumbWhere’s URL shrinking service ( tny.tw ).
You can get a ThumbWhere account at http://thumbwhere.com
Also you don’t have an account you can always MMS images, video and audio to +61-447-100-293 and ThumbWhere will publish it anonymously to the public feed.