Jump to content

Search the Community

Showing results for tags 'tcp client'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 1 result

  1. Hi, I am making a determined effort to migrate a particular application of mine over the fence to OO, but I would like to be "herded" towards using the correct or proper design pattern(s). This application of mine is a TCP Client app that allows the user to connect to one (1) test server as to display test data in various forms (i.e. tabular, time-histories, gauges, etc.) using a single tab control. There can be up to ten (10) such Clients logged in at one time to the same Server. I have read recently that several folks on NI & LAVA forums advise to move away from the tab control and to use sub panels instead. Combine that with this web page's neat UI plugin example, I seem to be getting close to finding the proverbial "light switch" in the dark room, but ... it could be something else .... Some notes: I do have LabVIEW 2012 at my disposal. The test server is written in C++. Down the road a bit we may need to encrypt the XML stream so I may need to put a LabVIEW web service in between the Server and each Client using SSL - if that's a future design bit to note here but not as important as the basic environment or use case of a TCP Client that displays data via several types of displays - which the display types will only grow in the near future as we all have experienced. So adding different displays should be as "easy" as possible. Note: My question was originally posted here, but I was advised to post it here on LAVA for a more experienced architect to respond. Thank you very much in advance !!! CS
×
×
  • Create New...

Important Information

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