Remove deprecated custom packet API from INetwork

Usage of this API was already discouraged, since all official
VATSIM packet handling should be in vatlib itself or for custom defined
packets in CNetworkVatlib. If a new custom packet needs to be added,
it should go into CNetworkVatlib directly and made available via normal
API methods to abstract the packets custom nature. The fact that
custom packets exist, should be kept internal. However, a debug message
is raised in case of an unknown custom packet in order to allow
detection and debugging.

refs #870
This commit is contained in:
Roland Winklmeier
2017-03-02 00:46:37 +01:00
committed by Mathew Sutcliffe
parent 7fde8eef07
commit ba1122533f
5 changed files with 6 additions and 37 deletions

View File

@@ -251,13 +251,6 @@ namespace BlackCore
//! @{
////////////////////////////////////////////////////////////////
/*!
* Send a custom packet.
* \pre Network must be connected when calling this function.
* \deprecated As a short cut you can use this slot directly, but it is better to implement the encoding in INetwork and add a new signal.
*/
virtual void sendCustomPacket(const BlackMisc::Aviation::CCallsign &callsign, const QString &packetId, const QStringList &data) = 0;
/*!
* Send a FSInn custom packet.
* \details FSIPI(R) queries, some example data below:
@@ -517,13 +510,6 @@ namespace BlackCore
*/
void textMessageSent(const BlackMisc::Network::CTextMessage &sentMessage);
/*!
* We received a custom packet.
* \deprecated As a short cut you can use this signal directly, but it is better to implement the decoding in INetwork and add a new signal.
* \sa CNetworkVatlib::customPacketDispatcher
*/
void customPacketReceived(const BlackMisc::Aviation::CCallsign &callsign, const QString &packetId, const QStringList &data);
/*!
* We received a FSInn custom packet.
*/