Table of contents
sl_cache 
- Access to sl_relay can be done on a per machine basis through an access list.
Control Process (Cache GET Process)
- The communication port for sl_relay is selected at random by negotiation.
- When the same host doesn't have both sl_relay and sl_cache, the negotiation and subsequent data communication might be tapped.
- If the negotiation or subsequent data communication is tapped, there is a possibility for the terminate command to be sent forcing a shutdown.
Cache PUT Server
- The Cache PUT Server disregards packets not coming from localhost.
Relay Process to Cache PUT Server
- The port and the connection password are decided by negotiation with sl_relay.
- The connection password is not used too strictly (it is possible to tap it). This is an advanced trial of a feature for a future version.
- Only data from the IP address and port number determined during negotiation is relayed to the Cache PUT Server.
- If the negotiation or subsequent data communication is tapped it is possible that false texture data might be transmitted by the Relay Process.
Counter: 2126,
today: 6,
yesterday: 1
Last-modified: 2008-12-21 (Sun) 03:29:18 (JST) (5599d) by gambled
