Fri 26 Feb 2010 03:57:15 PM UTC, comment #2:
Log shows that no long Poll should be pending:
2010-02-26 15:36:25+0100 [HTTPChannel,85,127.0.0.1] PokerAvatar: handlePacketDefer(1): POKER_LONG_POLL type = 167 length = 3
...
2010-02-26 15:36:26+0100 [HTTPChannel,87,127.0.0.1] PokerAvatar: handlePacketDefer(1): POKER_LONG_POLL_RETURN type = 168 length = 3
2010-02-26 15:36:26+0100 [HTTPChannel,87,127.0.0.1] PokerAvatar: longPollReturn([]):
2010-02-26 15:36:26+0100 [HTTPChannel,87,127.0.0.1] PokerResource: (x-forwarded-for:10.10.1.61, 10.10.1.44) render {"type":"PacketPokerLongPoll"} returns []
|
Fri 26 Feb 2010 03:35:10 PM UTC, comment #1:
Log shows that after PacketPokerTourneyRegister is handled:
2010-02-26 15:36:26+0100 [HTTPChannel,91,127.0.0.1] PokerResource: (x-forwarded-for:10.10.1.61, 10.10.1.44) render {"type":"PacketPokerTourneyRegister","serial":1,"game_id":135\
6}
2010-02-26 15:36:27+0100 [HTTPChannel,91,127.0.0.1] PokerAvatar: handlePacketDefer(1): type = POKER_TOURNEY_REGISTER(116) serial = 1 game_id = 1356
2010-02-26 15:36:27+0100 [HTTPChannel,91,127.0.0.1] PokerAvatar: handlePacketLogic(1): type = POKER_TOURNEY_REGISTER(116) serial = 1 game_id = 1356
Its response is handled throught longPollDeferred:
2010-02-26 15:36:27+0100 [HTTPChannel,91,127.0.0.1] PokerAvatar: sendPacket(1): type = POKER_TOURNEY_REGISTER(116) serial = 1 game_id = 1356
2010-02-26 15:36:27+0100 [HTTPChannel,91,127.0.0.1] [1]PokerExplain:explain: type = POKER_TOURNEY_REGISTER(116) serial = 1 game_id = 1356
2010-02-26 15:36:27+0100 [HTTPChannel,91,127.0.0.1] PokerAvatar: flushLongPollDeferred([type = POKER_TOURNEY_REGISTER(116) serial = 1 game_id = 1356]):
Which is confusing because POKER_TOURNEY_REGISTER is an incoming packet from the client, and no long poll should be pending.
Because the client send LongPollReturn before queuing any outgoing packet.
|