Hi Jeff,
Have you got any further idea on this issue? If there is any further
questions or anything we can help, please feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
BogeyGolf - 08 Jun 2007 13:07 GMT
Hi Steven,
Sorry for the delayed response. For some reason I did not see your response
until this morning. (Refresh must not have been refreshing).
Yes, I am looking into using an OO Database. Currently, db4o is the top
contender. However, I am not sure of its Client/Server capabilities.
I simply want the ability to work fully OO. In other words, have an object
model of entity objects to be shared/synchronized among clients on a LAN. I
can't imagine I am alone in this search for answers.
Thanks, Jeff
Steven Cheng[MSFT] - 11 Jun 2007 16:17 GMT
Thanks for your reply Jeff,
Yes, using WCF can help save much time on creating the communication and OO
model. For the DB4O you mentioned, I'm not sure on it. Anyway, if you get
any progress or need any further help, please feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Steven,
Thanks for helping me with this issue.
> From your description, you have multiple windows form applications deployed
> on multiple machines in a local intranet environment and will need to
> synchronize some certain status data at runtime, correct?
Yes, there will be about 5 or 10 clients all running the same Windows Forms
application that will be sharing configuration data and status data.
> As for the shared and hierarchical data, are they freqently changed(by all
> those client winform programs or may receive updated data from a central
> backend data store)?
The "configuration data" can be modified (CRUD) by any of the clients. The
"status data" will generally emanate from a single source (e.g. server). The
"configuration data will not be changing frequently, but it will change, and
each client will need access to CRUD operations.
> If the data is frequentely changed and will need to be sychronized among
> all those clients whenever any client node update it, I think you may
[quoted text clipped - 4 lines]
> serialize them when need to transfer between multiple client nodes over
> network.
Yes. However, I would rather not "home brew" all of the middleware
(locking, concurrency, guids, callbacks, etc.). I was hoping WCF would
rescue me.
> ** Use raw socket interface to transfer the data between the center data
> center and all those client nodes. Thus, the data center can work like a
> UDP server which can receive update request from all client nodes and
> whenever one node update the shared data, center can use UDP "broadcast" to
> send notification to all other client nodes.
Yes, I am considering using multicast for "Status Data" distribution.
> Using socket here is for performance consideration. Of course, other
> districuted service like remoting or WCF can also do the same job, but may
> involve some additional overhead.
I am now looking at the OO Database "db4o" for this job. However, I am not
sure if its Client/Server mode will work well for this scenario.
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
Thanks, Jeff