08-28-2019 01:41 AM - edited 08-28-2019 01:42 AM
Hi,
Can anyone explain the status of Network Streams and Network Shared Variables in NXG?
What is the idea behind a Data Communication Compatibility pallette? Is it going to be deprecated somewhere down the line?
Are these technologies still a viable choice for use in newly developed applications that require maintenance for the coming say 5 years?
What would be the alternative technologies that should be used in their place?
08-28-2019 09:25 AM
I wouldn't write an application that is going to be around and need to be maintained with any language that is still basically in its beta release.
08-29-2019 07:23 AM
Hi Bob,
I agree with that statement, except for the web module part since it doesn't have a CG counterpart.
But I'm talking about using the technologies mentioned in the NXG compatibility pallette in CG applications. What would be the future impact of a choice for these technologies in new CG based applications when migrating to NXG at some future point in time.
How long will the compatibility pallette exist?
Is there a chance that it might be removed just in the version we would then like to migrate to?
What is the meaning of the word "compatibility" in this context?
I hope this clarifies a bit better what answers I seek.
08-29-2019 09:01 AM
As i understand it, Network streams is basically a wrapper of some TCP/IP functions in much the same way Channel wires is a wrapper of some Queue functions.
I bet they'll be around, and if not atleast supported for many years, and if even that would fail (but then we're 10+ years into the future) you can easily switch to standard TCP/IP.
/Y
08-29-2019 11:50 AM
andre.buurman@carya wrote:
Can anyone explain the status of Network Streams and Network Shared Variables in NXG?
I'm pretty sure Network Published Shared Variables are supposed to be gone in NXG. I do believe there was a "Tag API" library that is supposed to replace them.
I have not heard anything on the Network Streams. But I imagine, based on a CAB I was on a few years ago, NI will eventually start working on a "Stream API" that could replace the Network Streams (and possibly Queues, RT FIFOs, etc.). But this is pure speculation.
So if you are thinking long term, I would probably stick with the TCP/IP and UDP functions. I prefer using the TCP/IP anyways.
08-29-2019 02:28 PM
@crossrulz wrote:
andre.buurman@carya wrote:
Can anyone explain the status of Network Streams and Network Shared Variables in NXG?
...
So if you are thinking long term, I would probably stick with the TCP/IP and UDP functions. I prefer using the TCP/IP anyways.
Ditto that!
They should around a good long time and if we write the code that uses them, we can fix the problems and NOT have to wait for a bug fix and NOT have to worry about them being dropped (Like BridgeVIEW Tag engine, SoftMotion, etc)
Ben
08-30-2019 03:26 AM
Thanks all for sharing you thought and opinions.
08-30-2019 07:50 AM
andre.buurman@carya wrote:
Thanks all for sharing you thought and opinions.
You are welcome.
Please let me put my thought another way...
"If I can do a ctrl-e, I can fix it. If not I am at the mercy of others."
Ben