Comments on: MSDN Magazine Smart Client Article

By: udidahan

udidahan — Wed, 22 Apr 2009 11:56:21 +0000

ChrisR,

Yes, nServiceBus was used for the pub/sub and handled hundreds of subscribers.

There were differences in the object model that was bound to view objects and that which was persisted server-side (the domain model).

Hope that helps.

By: ChrisR

ChrisR — Wed, 22 Apr 2009 09:08:23 +0000

Just to clarify, did you use NServiceBus for the pub/sub between client and server? And if that is the case, does that mean that NServiceBus is capable of supporting hundreds of subscribers?

Also, are there any differences between the client side domain model and the server side domain model?

By: udidahan

udidahan — Tue, 14 Apr 2009 09:09:19 +0000

J – that’s awesome!

By: J Healy

J Healy — Tue, 14 Apr 2009 04:16:03 +0000

http://blogs.msdn.com/jmeier/archive/2009/04/13/performance-hot-spots.aspx?CommentPosted=true#commentmessage

By: udidahan

udidahan — Mon, 13 Apr 2009 07:48:55 +0000

I did have some discussions with P&P on these topics but I’m afraid none of it has worked it’s way in to either Prism or the other guidance.

By: J Healy

J Healy — Sun, 12 Apr 2009 23:02:31 +0000

Sounds like quite the ’saga’. As you mentioned to Don above there’s more than could fit into a single diagram or project, but much of the architecture and concerns that emerged from the tale you recount appear fundamental to a collaboartive, sometimes-connected applications with demanding notification requirements. If that is in fact the case, then have you had any discussions with the P&P group relative to Prism and other P&P guidance?

By: udidahan

udidahan — Thu, 09 Apr 2009 20:55:22 +0000

Don – as you can probably imagine, there’s more than could fit in a single diagram or project.

Mike, I’ve found that patterns really do survive technological evolutions and “revolutions”.

Daniel, nServiceBus was eventually used on that project. I chose not to call that out explicitly in the article seeing as it’s a Microsoft publication.

By: Daniel

Daniel — Mon, 06 Apr 2009 23:14:28 +0000

What was the reason why WCF is chosen in favor of the usual suspect (NServiceBus). Espeically considering MSMQ is the transport of choice, is there any reason why NServiceBus architecture might’ve been a poor choice for this app? Maybe occasional connectivity puts too much stress on subscription sync?

By: Mike

Mike — Mon, 06 Apr 2009 16:56:16 +0000

The Lessons Learned was absolutely a most entertaining read. Real life proof that it’s incredibly complex to get WCF to work they way you want. I had to laugh. Seems the beginning of the article could have been written about DCOM or COM+. Same pain in each of those technologies. Still amazing that the approach of using Delphi 7, COM+, and MIDAS is relatively painless and you get the same results with a fraction of the code.

By: Don Baechtel

Don Baechtel — Sat, 04 Apr 2009 17:33:24 +0000

Do you have a sample project and a diagram that demonstrates your final results? That would be very helpful. THANKS.

By: Lee Campbell

Lee Campbell — Wed, 01 Apr 2009 07:25:33 +0000

Pretty good article. I hope your next project uses WPF. Sounds like a lot of plumbing in WinForms to get it to play nice.

By: Niraj

Niraj — Mon, 30 Mar 2009 05:23:05 +0000

Awesome as usual!!!