Home | Trees | Indices | Help |
|
---|
|
IBB used to transfer small-sized data chunk over estabilished xmpp connection. Data is split into small blocks (by default 3000 bytes each), encoded as base 64 and sent to another entity that compiles these blocks back into the data chunk. This is very inefficiend but should work under any circumstances. Note that using IBB normally should be the last resort.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from |
|
Initialise internal variables.
|
Register handlers for receiving incoming datastreams. Used internally. |
Handles streams state change. Used internally. |
Handles opening of new incoming stream. Used internally. |
Start new stream. You should provide stream id 'sid', the endpoind jid 'to', the file object containing info for send 'fp'. Also the desired blocksize can be specified. Take into account that recommended stanza size is 4k and IBB uses base64 encoding that increases size of data by 1/3. |
Send next portion of data if it is time to do it. Used internally. |
Receive next portion of incoming datastream and store it write it to temporary file. Used internally. |
Handle stream closure due to all data transmitted. Raise xmpppy event specifying successfull data receive. |
Handle stream closure due to all some error while receiving data. Raise xmpppy event specifying unsuccessfull data receive. |
Handle remote side reply about is it agree or not to receive our datastream. Used internally. Raises xmpppy event specfiying if the data transfer is agreed upon. |
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Thu Sep 25 18:45:12 2014 | http://epydoc.sourceforge.net |