Transfer Manager - Revision history

Poppy Linden at 23:30, 26 May 2010

2010-05-26T23:30:33Z

← Older revision		Revision as of 16:30, 26 May 2010
Line 12:		Line 12:

	The [[TransferAbort]] message can be sent from either side to end a transfer. The message is sent in response to incorrect accounting information, reliable packet delivery failure, or too many delayed packets.		The [[TransferAbort]] message can be sent from either side to end a transfer. The message is sent in response to incorrect accounting information, reliable packet delivery failure, or too many delayed packets.

			[[Category:Assets]]

Rob Linden: +{{ViewerArchNav}}

2006-11-29T08:38:12Z

+{{ViewerArchNav}}

← Older revision		Revision as of 01:38, 29 November 2006
Line 1:		Line 1:
			{{ViewerArchNav}}

	The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message. The source parameters are thrown away, and the client process creates an appropriate LLTransferTarget instance which copies the target parameters.		The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message. The source parameters are thrown away, and the client process creates an appropriate LLTransferTarget instance which copies the target parameters.

Jonathan Linden at 00:39, 28 November 2006

2006-11-28T00:39:13Z

← Older revision		Revision as of 17:39, 27 November 2006
Line 7:		Line 7:
	Textures are moved the through the [[Texture Pipeline]] -- not the transfer manager.		Textures are moved the through the [[Texture Pipeline]] -- not the transfer manager.

	When the server has collected the requested data, it sends a [[TransferInfo]] message to the viewer, followed by as many [[TransferPacket]] messages as necessary to transmit all data. If a [[TransferPacket]] is received before the [[TransferInfo]], or out of order, the data will be stored and replayed once the information shows up or the preceding packets arrive. If too many [[~~TranserPacket~~]] are queued for delayed delivery, the transfer will be aborted.		When the server has collected the requested data, it sends a [[TransferInfo]] message to the viewer, followed by as many [[TransferPacket]] messages as necessary to transmit all data. If a [[TransferPacket]] is received before the [[TransferInfo]], or out of order, the data will be stored and replayed once the information shows up or the preceding packets arrive. If too many [[TransferPacket]] are queued for delayed delivery, the transfer will be aborted.

	The [[TransferAbort]] message can be sent from either side to end a transfer. The message is sent in response to incorrect accounting information, reliable packet delivery failure, or too many delayed packets.		The [[TransferAbort]] message can be sent from either side to end a transfer. The message is sent in response to incorrect accounting information, reliable packet delivery failure, or too many delayed packets.

Phoenix Linden at 02:22, 23 November 2006

2006-11-23T02:22:03Z

← Older revision		Revision as of 19:22, 22 November 2006
Line 9:		Line 9:
	When the server has collected the requested data, it sends a [[TransferInfo]] message to the viewer, followed by as many [[TransferPacket]] messages as necessary to transmit all data. If a [[TransferPacket]] is received before the [[TransferInfo]], or out of order, the data will be stored and replayed once the information shows up or the preceding packets arrive. If too many [[TranserPacket]] are queued for delayed delivery, the transfer will be aborted.		When the server has collected the requested data, it sends a [[TransferInfo]] message to the viewer, followed by as many [[TransferPacket]] messages as necessary to transmit all data. If a [[TransferPacket]] is received before the [[TransferInfo]], or out of order, the data will be stored and replayed once the information shows up or the preceding packets arrive. If too many [[TranserPacket]] are queued for delayed delivery, the transfer will be aborted.

	The [[TransferAbort]] message can be sent from either side to end a transfer.		The [[TransferAbort]] message can be sent from either side to end a transfer. The message is sent in response to incorrect accounting information, reliable packet delivery failure, or too many delayed packets.

Phoenix Linden at 01:50, 23 November 2006

2006-11-23T01:50:15Z

← Older revision		Revision as of 18:50, 22 November 2006
Line 1:		Line 1:
	~~{{ProtocolNav}}~~		The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message. The source parameters are thrown away, and the client process creates an appropriate LLTransferTarget instance which copies the target parameters.

	~~The LLTransferManager class is a throttled data transfer system which is used primarily by~~ the [[~~Asset System~~]] to ~~fetch assets from Second Life~~. ~~A transfer manager client makes a new instance of a class derived from LLTransferSourceParams~~, a ~~new instance of a class derived from LLTransferTargetParams,~~ and ~~issues the request~~ with a ~~[[TransferRequest]] message~~.		When the [[TransferRequest]] comes in, the transfer id is used as a primary key in the server to index the transfers. Since duplicates are discarded and the key should be unguessable, it should be safe to key on a client generated uuid in this case. Colluding clients generating identical keys will get one successful request and one client with a likely memory leak.

			Requests for file sources will fail. Requests for assets are constrained to assets which the viewer is allowed to request via asset id. Asset requests are never prioritized in the asset queue regardless of client specified priority. Requests for inventory items are constrained to the assets in agent or task inventory according to the client source parameters on initialization.

			Textures are moved the through the [[Texture Pipeline]] -- not the transfer manager.

	[[TransferInfo]]		When the server has collected the requested data, it sends a [[TransferInfo]] message to the viewer, followed by as many [[TransferPacket]] messages as necessary to transmit all data. If a [[TransferPacket]] is received before the [[TransferInfo]], or out of order, the data will be stored and replayed once the information shows up or the preceding packets arrive. If too many [[TranserPacket]] are queued for delayed delivery, the transfer will be aborted.

	~~[[TransferPacket]]~~		The [[TransferAbort]] message can be sent from either side to end a transfer.

	[[TransferAbort]]

Rob Linden: +protocol nav

2006-11-23T00:01:45Z

+protocol nav

← Older revision		Revision as of 17:01, 22 November 2006
Line 1:		Line 1:
			{{ProtocolNav}}

	The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message.		The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message.

Phoenix Linden at 23:03, 22 November 2006

2006-11-22T23:03:23Z

← Older revision		Revision as of 16:03, 22 November 2006
Line 1:		Line 1:
	~~Document~~ the transfer manager ~~messaging~~ and ~~make sure it does not allow arbitrary transfer of files~~.		The LLTransferManager class is a throttled data transfer system which is used primarily by the [[Asset System]] to fetch assets from Second Life. A transfer manager client makes a new instance of a class derived from LLTransferSourceParams, a new instance of a class derived from LLTransferTargetParams, and issues the request with a [[TransferRequest]] message.



			[[TransferInfo]]

			[[TransferPacket]]

			[[TransferAbort]]

Phoenix Linden at 01:33, 16 November 2006

2006-11-16T01:33:14Z

New page

Document the transfer manager messaging and make sure it does not allow arbitrary transfer of files.