I agree with you to some extent, but can you please define “very well” when you describe the seamless windows engine in Longhorn, or even the application publishing methodology for that matter? What use cases have you subjected it to? At Provision Networks, one of the deciding factors for our clients has been our detail-oriented approach to implementing the seamless windows hook, among other things. In fact, there are some aspects of it that we’re in the process of patenting. Perception is everything. There are more than one way in which seamless windows can be implemented, and the same goes for how apps are published, load-balanced, and accessed. Yes, one could build extensions on top of the upcoming Longhorn features, but considering Longhorn is one and a half years away and companies won’t even start implementing it for at least 6 months to one year following its release, it makes sense to perfect what we have to offer today, especially if we plan to continue to support Windows 2000/2003. For example, Many clients of ours are still managing a Windows 2000 TS platforms today, and there’s no guarrantee they will upgrade a year and a half from now.

Yes, in order to thrive in the post-Longhorn era, ISV’s must focus on many last-mile technologies that to this day have not yet been untackled. But this doesn’t mean they shouldn’t also perfect their existing technologies.

Peter Ghostine
Provision Networks, Inc.
www.provisionnetworks.com