Hello Howard, the sniffer thing has nothing to do with original topic, I was just wandering that some requests were having session marked as new, which actually shouldn't be the case. Or in other word, the naive understanding of session.isNew method is that it should only return true once. But it did to it multiple times. The was strange, and christopher and myself were talking about investigating it further.
Back to your question, filter is ok, too many filters are making stack traces fuller than needed, and the order of the filter could be a problem. Listener is asked _before_ anything happens. regards Leon On Mon, Apr 29, 2013 at 4:59 PM, Howard W. Smith, Jr. < smithh032...@gmail.com> wrote: > On Mon, Apr 29, 2013 at 10:54 AM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > > >> Even, the requests are keepalived they look to me as if they were > > >> executed parallel. At least from the chrome timeline. But its > > >> hard to tell without further investigation. > > > > Yeah, you might have to use a packet-sniffer. > > > > > definitely sounds like overkill. how much code you need to write for such a > thing, all because one would want to avoid using a filter??? >