Create Network Stream Reader Endpoint (G Dataflow)

You can organize multiple endpoints by adding segments to this name to ensure that you connect each writer endpoint to its corresponding reader endpoint. To do this, place a slash between each segment of the name that you specify in your inputs with the organization scheme of your choice.

For example, RT Target/Temperature/Writer and Desktop/Temperature/Reader describe the target the endpoint resides on, the type of data the endpoint streams, and whether the endpoint reads or writes data, allowing you to show which endpoints correspond to one another.

If you specify a name that already belongs to another endpoint on the same computer, the first endpoint runs and is created, but the second endpoint returns an error that you can see in error out.

If this endpoint resides on a computer that runs multiple applications using network streams, you must assign an endpoint URL to this endpoint instead of a name. This node returns an error in error out. Use the following syntax to prompt a connection between the endpoints and avoid this error: //host_name:context_name/endpoint_name.

You must designate a writer for your reader endpoint to create a network stream. You can create this network stream in the following ways:

• Wire the writer url input of this node.
• Use the Create Network Stream Writer Endpoint node and wire the reader url input.

If you do not wire the writer url of the Create Network Stream Reader Endpoint node or the reader url of the Create Network Stream Writer Endpoint node, your endpoints will not create a network stream and your nodes will wait for a connection indefinitely.

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

• Use allocate as needed if your application transfers non-scalar data and you cannot determine the maximum size of each data element before run-time.
• Use pre-allocate if your application transfers non-scalar data and you can determine the maximum size of each data element at edit-time. If a larger element is added to the buffer during run-time, additional memory is allocated dynamically.

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.