.net - Inheriting legacy COM architecture, is it any good? -


Our system looks like this:

One or more applications that include one or several in-process COM Components are (s), which communicate with some hardware from a com server (hope is understood - please ask if they need explanation)

due to the design decision This time the chime is lost, but I think:

  • generates a serialized access to a single COM server hardware Does not.
  • The OCX client makes application development easy.

My questions are:

  1. If we want to do it again, will we work in the same way?
  2. What is the NAT analogy?

Thanks for any comments or signs - R

You have the same service (Managed H / W and Com Service). You are talking to the customer service (ocx). It sounds like a very simple client server and I think it's okay - if he does, then what he needs to do.

Again, what about your goals in terms of architecting? Current architecture can not serve future goals (for example, you may require more flexibility in the client server call), so it may have to change - but without further information I would say that it was ok.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

Visual Studio 2005: How to speed up builds when a VSMDI is open? -

booting ubuntu from usb using virtualbox -