The Sockets Server gives a "Protocol panic" when it finds incorrect protocol module behavior.
|
0 |
An unknown request completed |
|
1 |
Protocol completed a connect request unexpectedly |
|
2 |
Unused |
|
3 |
Protocol completed a connect with data request unexpectedly |
|
4 |
Protocol completed a shutdown with data request unexpectedly |
|
5 |
|
|
6 |
Protocol made incorrect call to the server through a MSocketNotify function |
|
7 |
Protocol made call to NewDataL with bad aCount value |
|
8 |
Unused |
|
9 |
Protocol made call to DisConnect with connectionless socket |
|
10 |
Server could not get expected received data from protocol |
|
11 |
Protocol has returned an invalid TServerProtocolDesc |
|
12 |
Protocol has not implemented CProtocolBase::Error() |
|
13 |
Protocol has not implemented descriptor-overload of CProtocolBase::Process() |
|
14 |
Protocol has not implemented RMBufChain -overload CProtocolBase::Process() |
|
15 |
Protocol has not implemented descriptor-overload of CProtocolBase::Send() |
|
16 |
Protocol has not implemented RMBufChain -overload CProtocolBase::Send() |
|
17 |
Protocol has not implemented CProtocolBase::BindToL() |
|
18 |
Protocol has not implemented CProtocolBase::BindL() |
|
19 |
Protocol made call to MSocketNotify::ConnectComplete() on non-listening socket |
|
20 |
Protocol made call to MSocketNotify::ConnectComplete() when server has accepted maximum number of sockets |
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.