summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
676141b)
Knowing a peer's supported procotol type will come in handy once we
support more than one protocol. Also, peers may support specific
features which they can now report via the new accessor.
};
LegacyPeer(AuthHandler *authHandler, QTcpSocket *socket, QObject *parent = 0);
};
LegacyPeer(AuthHandler *authHandler, QTcpSocket *socket, QObject *parent = 0);
+
+ Protocol::Type protocol() const { return Protocol::LegacyProtocol; }
void setSignalProxy(SignalProxy *proxy);
void setSignalProxy(SignalProxy *proxy);
using Peer::dispatch;
RemotePeer(AuthHandler *authHandler, QTcpSocket *socket, QObject *parent = 0);
using Peer::dispatch;
RemotePeer(AuthHandler *authHandler, QTcpSocket *socket, QObject *parent = 0);
- virtual ~RemotePeer() {};
void setSignalProxy(SignalProxy *proxy);
void setSignalProxy(SignalProxy *proxy);
- QString description() const;
+ virtual Protocol::Type protocol() const = 0;
+ virtual QString description() const;
+ virtual quint16 enabledFeatures() const { return 0; }
bool isOpen() const;
bool isSecure() const;
bool isOpen() const;
bool isSecure() const;