Changes

Content can be transferred with a custom protocol over the network. This is intended for use with local [[LDN_services|ldn]] networks, however the used IP addresses can be arbitary. This can be used for SystemUpdates via the above Send/Receive commands (which are then used via [[NS_Services#ns:su|ns:su]]). Application content can also be transferred, which uses a similar (?) protocol.

Content can be transferred with a custom protocol over the network. This is intended for use with local [[LDN_services|ldn]] networks, however the used IP addresses can be arbitary. This can be used for SystemUpdates via the above Send/Receive commands (which are then used via [[NS_Services#ns:su|ns:su]]). Application content can also be transferred, which uses a similar (?) protocol.

Task [[#Cmd69|creation]] for Receive will eventually use the input addr/port with [[Sockets_services|connect()]], while the Send version will eventually do the same with [[Sockets_services|bind()]]. Hence, Receive system = client, while Send system = host.

Task [[#Cmd69|creation]] for Receive will eventually use the input addr/port with [[Sockets_services|connect()]], while the Send version will eventually do the same with [[Sockets_services|bind()]]. Hence, Receive system = client, while Send system = server.

Messages (requests/replies) begin with the following 0x10-byte header, then any associated data.

Messages (requests/replies) begin with the following 0x10-byte header, then any associated data.

! Offset || Size || Description

! Offset || Size || Description

|-

|-

| 0x0 || 0x4 || u32 magicnum. Must match 0x7152444c (request messages, normally from the Receive system) or 0x7352444c (replies, messages normally from the Send system). Code validating the magicnum always checks both magicnums, not an individual one.

| 0x0 || 0x4 || u32 magicnum. Must match 0x7152444c (request messages from the Receive system) or 0x7352444c (reply messages from the Send system). Code validating the magicnum always checks both magicnums, not an individual one.

|-

|-

| 0x4 || 0x1 || u8 ID. The reply ID must match the request ID.

| 0x4 || 0x1 || u8 ID. The reply ID must match the request ID.

|}

|}

After the header is the associated data for size0 and size1, then the message-specific data if any. Generally size0 is 0, when receiving the data for size0 the received data is unused.

After the header is the associated data for size0 and size1. Generally size0 is 0, when receiving the data for size0 the received data is unused.

Messages:

Messages:

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|-

|-

! ID || Request size0 / data || Request size1 / data || Request-specific data || Reply size0 / data || Reply size1 / data || Reply-specific data || Description

! ID || Request size0 / data || Request size1 / data || Reply size0 / data || Reply size1 / data || Description

|-

|-

| 0x1 || 0x0 || SystemUpdate Meta [[#Cmd69|ContentMetaKey]] || None || 0x0 || 0x38-bytes, unknown. || None || This is the first message used by SystemUpdate.

| 0x0 || 0x0 || 0x0 || 0x0 || 0x0 || Tells the server to exit.

|-

|-

| 0x3 || 0x0 || 0x10-bytes, unknown. || None || 0x0 || 0x8-bytes: two size u32s. || Two blocks of data with the sizes specified by the u32s. || This is presumably used by Application-Delivery. The two blocks of data are used as the buffers for [[ETicket_services|es]] ImportTicket.

| 0x3 || 0x0 || 0x10-bytes, unknown. || 0x0 || 0x8-bytes: two size u32s. Then two blocks of data with the sizes specified by the u32s. || This is presumably used by the client for Application-Delivery. The two blocks of data are used as the buffers for [[ETicket_services|es]] ImportTicket.

|}

|}

[[Category:Services]]

[[Category:Services]]