How to make a multi to one notifier

[Eugen_Graf]

You will find me everytime in my forum www.labviewtutorial.eu

Performance test? Yes, it works good, I built it in a big project (for my work), and made a web-chat with this pattern. Both of them work very good, take about 1% CPU and less RAM.

Why do you ask about performance? One thing I would change in this pattern. I would replace String-Package-Identifiers to Enum-Typedef with IDs, becuse I think String comparison is much more slower as Enum comparision.

[alex.]

Originally, I also plan to make a project like this. And intend to make it a  multi - thread design, each thread will have its own queue. May be each topic has its own thread and queue.  All the queues may be dynamically assigned. The design  has not completed the yet. If your design is already very satisfied, I will reconsider it. Because in this parttern, the application is not facing the communication directly, so the performance is very important. May I know how big is your project. Thanks. You are the owner of such forum. That is great.  My contact email is  Turbot_yu@hotmail.com

[Eugen_Graf]

My first project using this pattern was to make a GUI for a complex device with two interfaces supporting diffrent user languages.

The Web Chat I programmed with this pattern is to show features of this pattern to LV programmers. This web chat is online now and looks like ICQ. If you want I will let you test this chat. The dispatcher is installed on a web server and every user get a client.

In the future I have to make a project to make a network of test equipment for our company. It will have to support about 5-6 test devices (turn tables and temperature chambers) and about 10-15 different under test devices (products of our company). So I want to write drivers for each device at first (Init, Read, Write and Close) and than make one Slave-Loop per device. So this loops are modules of my project. Than I want to let user to select the Test Device(s), Under Test Device(s) and the Test Cycle (Calibration script). Than start user selected  modules and control them. If the script ends show and save all the results in a report.

Message Edited by Eugen Graf on 06-13-2008 03:36 AM

[alex.]

I made a setup of 3 PCs( A, B and C). All running on PubSub.

A connected to C.

B connected to C.

3 queue clients are running on 3 PC individially.

All the local(4) and remote (4) topic were subscribed on A and B.

Then I tried to change value on B. And found C will hang for a while then disconnect A and B. Please see the screenshot.

Does A and B subscribe too much or anywhere I should start to debug it. Thanks.

Message Edited by turbot on 06-13-2008 04:55 AM

[Eugen_Graf]

The remote feature is the newest one. I don't tested it well. But say me please why do you need this feature? It was made to debug the dispatcher PC from one other.

But I think I know what can happen if you have more than onedispatcher andconnect remotely one to the other. Be sure that messages you send remotely are not defined twice. Elese you can get a undlss loop, because one messagewill be sent from one dispatcher to other and back and so on.

In really it's enogh for almost all projects to use only one Dispatcher without to connect remotely. Can you say me what do you want to do with this patten?

So you can start one dispatcher on PC A, which have User Interface and is the main. Than you can start on PC B and C two or more TCP/IP Clients which will use the dispatcher from PC A. S you don't need a dispatcher on every PC. One PC is Server, and all other are Clients.

Message Edited by Eugen Graf on 06-13-2008 05:28 AM

[Eugen_Graf]

You have also to give different names for topics on different PCs. Be sure it's done. Than you should get no problems, esle you will get the endless loop problem, because dispatchers will send the same message back and forth.

[alex.]

The reason is there may be several PC on network need to communicate, one is the database master(as admin), another is the communication one facing all the remote hardwware, also the one facing all the HMI client. Sometime with their redundancy partner also.

May you give more details of 'Be sure that messages you send remotely are not defined twice.' Thanks.