> On Sep 7, 2016, at 9:16 PM, Sudheer Vinukonda > <sudheervinuko...@yahoo.com.INVALID> wrote: > > > >> On Sep 7, 2016, at 8:48 PM, James Peach <jpe...@apache.org> wrote: >> >> >>> On Sep 7, 2016, at 8:30 PM, Sudheer Vinukonda >>> <sudheervinuko...@yahoo.com.INVALID> wrote: >>> >>> I was replying to this - >>> >>>> "I don’t think this is any different from allowing SPDY or HTTP/2 to mark >>>> their transactions as non-internal." >>> >>> Marking Spdy/H2 as non-internal works because of the special handling done >>> via FetchSM. With the proposed new API, you are intending to mark plugin >>> generated requests as non-internal. My point is that it'd likely cause >>> issues. I'll try to find some time to dig and provide specifics. >> >> That would be great, because I’m struggling to see the special case here :) > > Below are a couple of recent related jiras, there's likely more. > > TS-3404 > TS-3777
Hmm, that’s a bit scary. It doesn’t seem like checking whether a transaction is internal is a very reliable fix. I guess there is a corresponding hack for HTTP/2 so it can be non-internal and not fall into this hole? J
