I'm noticing some funky behavior w/ OnStopRequest callbacks. First a
question...
what are the current semantics surrounding OnStartR() and OnStopR()
callbacks? We used to maintain the guarantee that you would never
receive an OnStopR() w/ out a preceeding OnStartR(). Is that rule still
maintained? I *think* it is, but want to make sure I'm clear up to
speed.
Back to the funkiness. Should hitting the reload or the stop button fire
an OnStopR() up the chain of consumers? If so, I'm not seeing this
happen in the multipart/x-mixed-replace stream converter case. If I'm
receiving a bugzilla query for example, and I hit reload or stop, the
mixed converter's nsMultiMixedConv::OnStopReqest() never gets called,
and subsequently bad things start happening (corrupt content, crash,
other randomness). Is this the multi mixed converter's problem somehow?
Have semantics changed in this area? Is HTTP receiving OnStopR() in
response to a reload or stop button being pressed?
Thanks,
Jud
