Communication between two classes

Question

4.00/5 (1 vote)

See more:

I am having a network class and a dialog class.I have to send the data recieved in network class to dialog class but not direcly i.e it should not be tightly coupled with my dialog. Help me out..............

Posted 12-May-11 21:43pm

Rocker Gang

Add a Solution

Comments

Sergey Alexandrovich Kryukov 13-May-11 4:05am

The question makes some sense, my 4.
--SA

2 solutions

Solution 2

As suggested, your network class should run in a working thread, while the GUI runs in the main one, see the following Newcomer's article: "WorkerThreads"[^] (you may find a lot of useful assays in his webpage).

You may use, for instance, properly synchronized shared resources to hold incoming and outcoming data and messages (via, for instance, PostMessage) to make the network class notifying for data arrival.

Posted 12-May-11 23:19pm

CPallini

Updated 12-May-11 23:22pm

v3

Comments

Albert Holguin 13-May-11 10:59am

I don't know if synchronize is the correct term here... considering PostMessage is an asynchronous message... but proper methodology nonetheless, my 5...

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-05-12T22:04:00

Solution 1

This is really bad idea. Network data is coming and coming but dialog stays modal until the user closes it. There is apparent controversy between network stream and modal behavior. You need to run all your network application-level protocol in a separate thread (on server side typically in two threads, one accepting new connections, another one performing exchange with clients' network streams) — isn't this logical?

Your concern about tight coupling is absolutely correct.

So, your network events can notify UI, and the UI should show some data, status, etc. As I say, modal behavior hardly fits the networking design. Better show data in something like list box or list view. You can implement walking by the lost items and displaying some detail of data in some other control.

—SA

Posted 12-May-11 22:04pm

Sergey Alexandrovich Kryukov

Comments

Olivier Levrey 13-May-11 4:18am

Good advices. My 5.
OP is maybe using a non-modal dialog though (he didn't say). Anyway the general ideas about threading and data updating are good.

Sergey Alexandrovich Kryukov 13-May-11 4:31am

Thank you, Olivier.

I know you C++ people often discuss non-modal dialog, but to my taste is sounds like oxymoron. Don't you feel the same way? As to any modal behaviour, I think their use should me strongly minimized, mostly reduced to well-known cases like "open file", "save file", etc.

Anyway, non-modal window would work a little better on the notification from the network thread, but only a bit; it's also not very adequate...
--SA

Olivier Levrey 13-May-11 4:46am

I personnaly don't like non-modal dialogs much and use them in very rare cases. Users find them annoying, they don't know where to put them. However I do use modal dialogs quite often. Not only for loading/saving files: our users like wizards. They are mostly biologists and are often affraid about computers, so they appreciate to be guided. The ultimate rule could be: do not show them more than one button at a time otherwise you would stress them!

Sergey Alexandrovich Kryukov 13-May-11 4:57am

The last principle is very wise, but the wizard is maybe not the best solution; people just used the them.
Good to know your opinion on dialogs, thank you.
--SA

CPallini 13-May-11 5:15am

My 5.

Sergey Alexandrovich Kryukov 13-May-11 6:50am

Thank you very much.
--SA