I thought the UI for the next version of Connect was convered by the NDA and Fang mentioned not to put any shots up. Should you take the presentation down?

this does not seem to be covered by an NDA so it should be good to go as is. Thanks for waving a flag though.

Note: long reply ahead.

thanks Nigel (and I type this while I listen to your preso at the same time), I actually got this URL from the Flash Media List and also cross checked it in the Adobe Experts Portal where it wasn't marked as NDA so I assume it's good to go?
I really think that CoCoMo looks awesome (hoping to see a beta invite soon in my inbox ;-) and that you guys have done a great job. I can also see how a pure clientside development SDK will work well and how it leaves opportunities left for FMS yet at the same time it's clear that it will eat deeply into FMS's featureset and it will direct people away from the platform and onto CoCoMo. And that's fine I guess (and Adobe never made a good job of selling FMS's strengths outside video delivery) but it remains to be seen if more opportunities for developers are created by this than will be taken away. And that one is tricky to judge even further down the line.
Lastly I really ought to get my slides and pics from MAX online as they clearly show that Pacifica and CoCoMo will between themselves cover almost all of what FMS can do minus the pure video delivery features. We all get a clear sense of where Adobe is heading but I haven't yet decided if it's a good one or not. If FMS wasn't around I'd probably be the happiest Flash developer around but as things stand I see Adobe pushing deep into developer territory, not only with CoCoMo but also on the AMP front (and I can name a few more examples like that). But that one's for another blog post ;-)

No hard feelings here by any means, but Adobe could be walking a fine line between enabling developers and competing with them. On the flipside I understand that if you want us to leverage all the great work that's gone into Connect this is probably a pretty obvious way to do that.

Thanks Brian,
we'll certainly know more further down the line but I have equal dilemmas as a poster on Nigel's blog. We're trying to sell a Flex whiteboard component for FMS - maybe not something that we should invest much more time into if we can soon drag and drop one in 5 minutes. The only advantage I see for FMS in our case is the backend integration between FMS and 3rd party systems that most clients require.
As for LCDS - I don't see that as any great competition to FMS, especially not with the price tag that multi CPU versions currently have.

cool, that's the kind of stuff we like to hear :-)

I agree with you Burt, it's great to see that resources are being put into the RTC space and the CoCoMo framework looks excellent. But I also feel that FMS is being left out in the cold in some respect unless we will see a similarly up to date component set or framework being put into FMS. The CoCoMo components are what many FMS developers have been waiting for (we have not had an FMS component update since FCS 1.0 5 years ago) but it seems that they cannot be leveraged on our own servers.
If you look at CoCoMo on its own then it all looks pretty sweet, but run it alongside FMS and the picture changes for me. I can;t help but feel that FMS deserves a similar update but that's probably wishful thinking as Adobe is clearly (and maybe I should say once again) keeping the best bits to themselves.