Okay, so... I haven't actually looked at WCF before, but I am not going to tell him... feel free to skip the basics on me ;) ... I need to decide if I want to know... I'm not hear for the sessions to actually teach me stuff.
WCF first... a lot of talk about it being easier to set up, but explained in terms that do not immediately relate to me. I'd love to have him show a 'before and after' sample, that'd make it instantly obvious. Ah, okay... an example after the opaque description... should have done that the other way around. Excellent, default bindings look to make it a lot easier... I can remember feeling it was way too complicated for what I was achieving when I gave it a quick try once... I might actually be enticed to try again.
I wish I could explain this all a little better, but I do not think I know the problem domain well enough to express this in a simple fashion. Basically it looks like there is a lot of useful default behaviour for setting up service endpoints and behaviour.
Built-in service discovery using UDP or a discovery server on the network. I wish we didn't have a roll-our-own server architecture now, because this would take away a lot of the pain we are working through right now.
Hey, the presenters' desktop just taught me something useful. I can have the taskbar to the left of the screen giving me more vertical space on the limited size of this screen... excellent!
Router service... sounds good... maybe this can be used to implement transparent back-end redundancy? He mentions something about content-based routing, maybe that means it can also be made 'sticky' for a given client app to keep 'state' and 'session' in line. I will have to learn more about this stuff. Gonna be a pain to migrate from what we have already invested a lot of time in, but it'll be standard technology supported by Microsoft with many features we will never retrofit into our own solution. Main problem would be that our existing system is object-based, where WCF is interface method based.
Running low on battery... this may end up truncated before the end of the session. I like router filtering config. Very useful for migrating apps between versions of a service where some apps may not be able to work with the new version when it is first released.
He's going to do WF now, but since the battery is low, I will post this now. WF is a little further from what I need for anything right now, although I'm sure he'll manage to convince me I need it right now.

Post new comment