Jump to content

Eugen Graf

Members
  • Posts

    432
  • Joined

  • Last visited

Posts posted by Eugen Graf

  1. Ok, now I understand it. So you have a sender task for each publisher (service) on the dispatcher side. Why not one for all? My dispatcher does all, registration, unregistration an sending in one loop, but each service has own receiver loop. I think this is the biggest difference between our realisations of this pattern. The second less difference is you use functional global variable for the client list, but I don't.

    For all, I think it's very interesting pattern, which can be used for dynamic applications, where many publishers and subscribers can communicate to each other.

    Thank you :worshippy:

  2. No I didn't :thumbup1: Great minds think alike eh? :yes:

    You talk about it being in the repository, but I'm unable to find it. Maybe it was lost along with the "The Great Crash" since the posts seem from quite a while ago. I wouldn't mind taking a look. Do you have a link?

    Yes, it was lost after updating LAVAs software (I think). Here you can download my version:

    http://labviewportal...hp?f=19&t=9#p19

    I see you also talk about "Topics" which suggests (to me) a single server with segmented data filtered for the particular subscribers (classic pub/sub). I think mine is more content-based where each "Topic" is in fact a dedicated server and after registration or subscription, the Dispatcher has little to do with data.

    I think it's the difference to your dispatcher. I send all the data to the server(dispatcher) and the dispatcher sends them to subscribers. It makes some advantages like debugging on one place, but disadvantages like more traffic on the server side.

    But, sorry, I don't see where you send your data from one publisher to many subscribers. TCP/IP is one to one connection, so you have to send your data twice if you have two subscribers. I can't see any for-loop in TCIP Write.vi.

    EDIT: my the web chat project (based on Pub/Sub Pattern) may be interesting to you http://lavag.org/top...uss-eugen-graf/

  3. Sorry if anybody didn't understand my last message. I mean LabVIEW isn't compatible with poor display resolutions, which netbooks have. As you can see on my screenshot the three buttons are not visible on the screen.

    I have DELL Mini 10 with Ubuntu installed. I'm very happy with this netbook :thumbup1:

  4. Irene, sorry, I don't know if I should say that, but:

    the design of both .com and .cn sites is "not the best"

    on the .cn site I see only a (left)half of them on my screen with a big resolution

    you may think on the redesign of your logo

    Of course it's only your thing...

  5. I just downloaded it, tried it, and was going to suggest it! :thumbup1:

    LabVOOP may be a bit much for someone new to LabVIEW though...

    OFFTOP There is no much LVOOP, only a clever cluster, no more. So it's understandable by any.

    TOTOP: So you may try to collect all connections into an array and send to all in a for-loop (if you use TCP) and send a broadcast to all if you use UDP (but without ack).

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.