As you can see the packets per second graph is rather more interesting.
When we look at what the traffic actually is (note: using "view -> time display format -> time of day" is useful), it's possible to see the same sequence of packets repeated during the long delay:
(C: client; S: server)
C -> S: Req: TranslateCoordinates
S -> C: Rep: TranslateCoordinates
C -> S: Req: GrabServer, QueryPointer
S -> C: Rep: QueryPointer
(* now, repeated seven times *):
* C -> S: Req: QueryPointer
* S -> C: Rep: QueryPointer
(* end repeated segment *)
C -> S: Req: UngrabServer
The whole segment above repeats hundreds of times during the long delay before the compose window appears.
I've attached a pcap trace containing one of these repeated segments so you can examine it easily without having to dig through the whole trace. Also attached is a text version.
As you can see the packets per second graph is rather more interesting.
When we look at what the traffic actually is (note: using "view -> time display format -> time of day" is useful), it's possible to see the same sequence of packets repeated during the long delay:
(C: client; S: server)
C -> S: Req: TranslateCoordi nates nates
S -> C: Rep: TranslateCoordi
C -> S: Req: GrabServer, QueryPointer
S -> C: Rep: QueryPointer
(* now, repeated seven times *):
* C -> S: Req: QueryPointer
* S -> C: Rep: QueryPointer
(* end repeated segment *)
C -> S: Req: UngrabServer
The whole segment above repeats hundreds of times during the long delay before the compose window appears.
I've attached a pcap trace containing one of these repeated segments so you can examine it easily without having to dig through the whole trace. Also attached is a text version.