Namespaces are defined in the document's root element

Communications with a Pipeline server is accomplished with the use of TCP sockets. There are 3 parts of the total packet structure. The first 4 bytes of a packet specify ...

At this stage, the server will authenticate the user information. If authenticated, the server will send back a SuccessfulAuthenticationPacket. If not authenticated ...

Both sides of a connection need to inform the other side once they have established the encryption ciphers, so that encrypted communications can begin. The following ...

This is an example of a DiffieHellman parameters packet 45428 45428 AES 128 161409185729581153775647009132494411332525 879318039955946978758100904429530726656032 187867234343861292704739684762474760744077 ...

Once the Pipeline application (client or server) has received the NetworkingAPIDiffieHellmanParametersPacket, it will use these parameters to establish its private ...

Upon connection, the server (the one who accepted the connection) will send over a NetworkingAPIDiffieHellmanParametersPacket to the client (the one who initiated ...

Once the other end's public key has been received, and one's own asymmetric keys have been established, the DiffieHellman algorithm is used to generate the shared ...

This step simply waits for the other end to send over their public key, in a NetworkingAPIPublicKeyPacket. Main.MichaelJPan 22 Mar 2005

First open a tcp socket. Main.MichaelJPan 22 Mar 2005

This is a packet that requests a file file request ${USER} ${PASSWORD} 17.0.0.1 37308 127.0.0.2 37308 Main.MichaelJPan 23 May 2005

This is a packet that encapsulates a part of a file file send ${USER} ${PASSWORD} 127.0.0.2 1096 127.0.0.1 1096 ${FILEURL} 0 65536 To specify that a packet is the ...

The server, immediately after the NetworkingAPICipherEstablishedPacket from the client, uses the credentials provided by the client in that packet to authenticate ...

Command packets allow a client to specify actions for the server to complete on its behalf. Some of these actions include load execute pause resume reset abort close ...

This packet allows for the server to inform the client of the status of workflows it is running on behalf of the user.

An example of such a public key packet. 45428 45428 308201a63082011a06092a864886f70d0103013082 010b02818100e5dab412c80776a5dd2c2d51ea6b97 2aecc55372a0b25227bae3dd3f6f5f46ca417b1e16 ...

Once the connection has been established, packets queued to be sent to the user while the user is logged out is sent.

Once the user has authenticated with the user, the server will send over information about the permissions the user has on the server in a NetworkingAPIUserPermissionsPacket ...

This packet provides the client with information about the permissions that the user has on the server.

If the client has jobs on the server from a previous session, the server will send over a NetworkingAPIWorkflowsSynchronizationPacket

This packet allows for a client and a server to synchronize on the workflows that the server may be executing on behalf of the user from a previous session.

Nightly builds If you are an internal user, you can grab a copy of the nightly build from /loni/mjpan/pipeline.builds/nightly/ on an internal LONI machine which mounts ...