Monday, February 28, 2005

Blog Marketing

Today I did my usual reading through the blogs I’ve subscribed to within Newsgator on the web. Two posts (by Jeremy Allaire and Eric Mack) referred to commercial ventures that were new and interesting to me. With both (Brightcove and Koolspan), I wanted to keep informed as to how they go in the future and follow up on the commercial and technical details down the track. It was easy to find an RSS feed for Brightcove and this was added to my Newsgator subscription list. I tried for a few minutes to find a similar feed for Koolspan but couldn’t. This was frustrating as I wanted to get more information on their products some time in the future and just be reminded that they (and their products) exist every so often. This is useful to me as I’m interested in their offering, but just not now.

A product or commercial venture blog that has a couple of posts every month would be perfect. It reminds you of the company/product you’re interested in regularly but doesn’t get annoying with incessant commercial posts which would lead to the subscription being removed. I was actually a little bit surprised that a company with a new technology offering didn’t have any obvious RSS feeds.

Sunday, February 13, 2005


Mitch Denny asks whether anyone would like to see some Indigo content at Code Camp Oz. I reckon this would be great and am particularly interested in:

Currently I’m working on building a .NET API for connectivity into a SCADA system first developed in the late eighties. The server side runs on Solaris, SCO Open Server, Linux and Windows 2000/2003/XP. The implementation approach stays away from the RPC style and instead takes an asynchronous messaging approach to maximize performance and utilization of bandwidth. The design was influenced by reading the Enterprise Integration Patterns book. The key concepts were that communications are a Conversation between multiple parties and that the stack in RPC style comms is being used a store for conversation state. This lead to a realization that the program stack is so heavily ingrained as a concept in my mind, that I didn’t realize it was holding back my way of thinking about distributed systems.

Personally, I think the distributed objects approach still has plenty of legs even with all the SOA work going on at the moment. Its just a matter of finding an easy way for application programs that use distributed objects to not be hampered by using the stack as a conversation state storage mechanism and still be usable with other APIs that rely totally on the stack for their operation e.g. UI APIs, database APIs etc. Put in other words an “asynchronous distributed objects” direction is much more palatable to my sensibilities than the SOA direction.

The whole conversation/stack investigation and thought process has lead to the modeling of a Conversation as a base class in the application design mentioned earlier in this post. The application has specialized classes for long running application specific conversations and also a general purpose RequestReply specialization of a Conversation. The request/reply conversation is used for simple short application conversations where round-tripping doesn’t affect the application usability. The approach has worked very well so far, but the implementation is still in it’s infancy.

Getting back to the Indigo discussion, I’m currently skeptical with the whole SOA approach because it may end up just being RPC with angle brackets for the broad development community. The really interesting part of Indigo for me is the prospective of a clean attribute/annotation driven API and an easier way to implement heavily asynchronous systems easily. How asynchronous applications can be easily implementated using Indigo/SOA is the missing part of the puzzle for me at the moment.


Got this link via To me it smacks of arrogance and heavy-handedness. I can just imagine the people who are really into content/video piracy getting a feeling of justification that they are working on a crusade against “the man”, the corrupt establishment etc. The approach of gloating that they won a court battle by putting their message on the web site of the loser strikes me as being counter-productive in the long run. I am all for artists and producers of content getting paid for their sweat, talent and risk. Otherwise people won’t take the big risks because they won’t get the rewards. If the originators of content don’t get a benefit, we’re all worse off. But… technology changes our societies massively. So instead of fighting against the wave, why not ride it?

Why not instead take advantage of the massive reduction in distribution costs and easy access to huge world wide markets that the Internet/broadband enables and provide easy access to reasonably priced content so very few have any inclination to get access to pirated content. This is effectively what happened with itunes, even though the pricing is still way too high. Give people an easy and reasonably priced option and they’ll go to in droves. “Reasonably priced” means something totally different in a broadband enabled world, where the distribution costs for “bits”/content is “stuff all” (i.e. close to zero).