/usr/include/gloox/bytestreamhandler.h is in libgloox-dev 1.0.13-3build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 | /*
Copyright (c) 2006-2015 by Jakob Schröter <js@camaya.net>
This file is part of the gloox library. http://camaya.net/gloox
This software is distributed under a license. The full license
agreement can be found in the file LICENSE in this distribution.
This software may not be copied, modified, sold or distributed
other than expressed in the named license agreement.
This software is distributed without any warranty.
*/
#ifndef BYTESTREAMHANDLER_H__
#define BYTESTREAMHANDLER_H__
#include "macros.h"
#include "jid.h"
#include "bytestream.h"
#include "iq.h"
namespace gloox
{
/**
* @brief A virtual interface that allows to receive new incoming Bytestream requests
* from remote entities.
*
* You should not need to use this interface directly.
*
* See SIProfileFT on how to implement file transfer in general.
*
* @author Jakob Schröter <js@camaya.net>
* @since 1.0
*/
class GLOOX_API BytestreamHandler
{
public:
/**
* Virtual destructor.
*/
virtual ~BytestreamHandler() {}
/**
* Notifies the implementor of a new incoming bytestream request.
* You have to call either
* BytestreamManager::acceptBytestream() or
* BytestreamManager::rejectBytestream(), to accept or reject the bytestream
* request, respectively.
* @param sid The bytestream's id, to be passed to BytestreamManager::acceptBytestream()
* and BytestreamManager::rejectBytestream(), respectively.
* @param from The remote initiator of the bytestream request.
*/
virtual void handleIncomingBytestreamRequest( const std::string& sid, const JID& from ) = 0;
/**
* Notifies the implementor of a new incoming bytestream. The bytestream is not yet ready to
* send data.
* To initialize the bytestream and to prepare it for data transfer, register a
* BytestreamDataHandler with it and call its connect() method.
* To not block your application while the data transfer lasts, you most
* likely want to put the bytestream into its own thread or process (before calling connect() on it).
* It is safe to do so without additional synchronization.
* When you are finished using the bytestream, use SIProfileFT::dispose() to get rid of it.
* @param bs The bytestream.
*/
virtual void handleIncomingBytestream( Bytestream* bs ) = 0;
/**
* Notifies the implementor of successful establishing of an outgoing bytestream request.
* The stream has been accepted by the remote entity and is ready to send data.
* The BytestreamHandler does @b not become the owner of the Bytestream object.
* Use SIProfileFT::dispose() to get rid of the bytestream object after it has been closed.
* @param bs The new bytestream.
*/
virtual void handleOutgoingBytestream( Bytestream* bs ) = 0;
/**
* Notifies the handler of errors occuring when a bytestream was requested.
* For example, if the remote entity does not implement SOCKS5 bytestreams.
* @param iq The error stanza.
* @param sid The request's SID.
*/
virtual void handleBytestreamError( const IQ& iq, const std::string& sid ) = 0;
};
}
#endif // BYTESTREAMHANDLER_H__
|