Geeks With Blogs

@sceptre1067
  • sceptre1067 @fesworks you're making a big assumption. like, was my question ever answered in the first place. :-) about 435 days ago
  • sceptre1067 I love how, instead of answering a question, the response is "I told you that last week" about 435 days ago
  • sceptre1067 @jasonbock well is does have a fun beat, but like most Joy Division songs, on the depressing side lyrics wise. about 436 days ago
  • sceptre1067 "A blindness that touches perfection, but hurts like anything else. Isolation." about 436 days ago
  • sceptre1067 "Me & Jesse, we left Ohio... left him bleeding on the valley floor..." about 436 days ago
  • sceptre1067 @cargoweasel yeah.. But the Mac Pro is the first desktop, in ages, makes me go ooooo, want. For looks alone. about 436 days ago
  • sceptre1067 Like how 4k support seems to be growing and yet... No 4k content I know of. about 436 days ago

Here in Flyover Country Talking about Project Management, Risk, and Statistics

Mainly going to use this as notes and such of what were discovering by overlaying WCF on an existing application.

So the set up...
In existence is...
1) a working web application
2) a server back end to support the web app (that we get to use for our needs)
3) a relatively complex hierarchy of classes (e.g. a inherits from b inherits from c, some interfaces are also referenced by c, as well as complex types.)

Our app will be a client/server application where the client will be in various offices located across a large geographic area. They communicate with the central office via a decent size WAN. Of course to do this communication we'll be using WCF.

O.k. issue number one...
we have a series of forms that have back end business objects with 3 layers of inheritance.

So first obvious "solution"...

Make a facade and have the service do the translation.

In other words look at the UI end and create a simplified object model based on that. One that will work easily as a data contract in WCF.

Then on the service end translate the incoming data into the needed business objects.

Upside - good separation,  don't have to touch business end
Downside - could be lot of upfront work if you're app will be doing a lot of back and forth between on screen and the client.

O.k. yes I started with the uber easy one... next what tools you can use if you have to serialize the actual business objects.

oh and code examples... as the above is just off the top of my head.

Posted on Wednesday, December 9, 2009 12:39 PM | Back to top


Comments on this post: WCF and Brownfield development (soon to be an on going series...)

No comments posted yet.
Your comment:
 (will show your gravatar)
 


Copyright © edgaralgernon | Powered by: GeeksWithBlogs.net | Join free