LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Network Stream Endpoint URLs

What is the intention of that network stream endpoint URLs do not comply with RFC 3986 - URI?

0 Kudos
Message 1 of 5
(2,749 Views)

There intention is to specify a uniform resource location, like all URLs.

 

A utility is a URL or name, but apparently, a name can't be used for nse's.

 

Maybe you can elaborate on what you want, why you want it, &c?

0 Kudos
Message 2 of 5
(2,691 Views)

Correct me if I'm wrong, but host_name:context_name is not a valid URI authority. My problem may seem nit-picky, but it's not.

 

At first, the structure of a URI is standardized. There is no need to argue about the benefits of standardization here.

 

The second point is that we are using Network Streams from .NET. In detail, we have a System.IO.Stream implementation for a Reader Endpoint and a Writer Endpoint, respectively. We would love to see such an interface in Measurement Studio. Unfortunately, as I already figured out, this will not happen. Therefore, we are constrained to Labview (32 bit) Interop.

 

Back to the actual problem: URIs in .NET are - like in many frameworks - URI objects, not strings. The advantages are obvious: Less magic, stricter interfaces, validation, access to URI parts and safe URI building, among others.

I was wondering why NI established this special host_name:context_name authority while ruining the stack in stronger typed environments.

 

Kind Regards,

Jonas

0 Kudos
Message 3 of 5
(2,678 Views)

 

I'm not saying you're wrong, I'm not into it that much. There might be other concerns then the ones you are describing. I'd think .net is not used for the implementation as it is now.

 

I don't know if you're being nit-picky. If you are that might very well be a good thing. The original post was a bit short to raise a discussion, so this might get it started...

0 Kudos
Message 4 of 5
(2,670 Views)

Sorry for the initial problem description. In fact, the "Endpoint URLs" are not unified resource locators. The RFC standard does not allow a string value after the colon ":" in the authority part (the part between "://" and the next "/"). This is not a .NET specific problem. Any URI validator will tell you that ni.dex://host_name:context_name/endpoint_name is not a URI. There must be a reason for that circumstance.

 

Thanks, Jonas

0 Kudos
Message 5 of 5
(2,662 Views)