Closed
Bug 33706
Opened 25 years ago
Closed 20 years ago
add 'callback channel' attribute to nsIChannel interface
Categories
(Core :: Networking, enhancement, P5)
Tracking
()
VERIFIED
INVALID
Future
People
(Reporter: warrensomebody, Assigned: darin.moz)
Details
We talked about this in our group meeting last week... We should add an accessor
to nsIChannel to allow us to set channel argument used in the event sink
callbacks. Right now, down deep in the transports, they do something like this:
mUserListener->OnStartRequest(this, mUserContext);
but if they could do this:
mUserListener->OnStartRequest(mUserChannel, mUserContext);
it would allow us to avoid a whole layer of nsIStreamListener implementation in
the channel implementations. (Look at nsFileChannel for an example.)
Note that this change might have be done hand-in-hand with one to change the way
load groups are managed since the OnStopRequest often removes the current
channel from the load group in addition to passing the OnStopRequest
notification upstream.
Reporter | ||
Comment 1•25 years ago
|
||
Enhancement for protocol writers.
Severity: normal → enhancement
Summary: add 'callback channel' to nsIChannel interface → add 'callback channel' attribute to nsIChannel interface
Target Milestone: --- → M20
Assignee | ||
Comment 5•20 years ago
|
||
this is now pretty much invalid given architectural changes in necko, but the
general idea might still be applicable to nsIInputStreamPump, but nearly all of
our channels do non-trivial stuff in OnStopRequest... usually releasing owning
refs to stuff. therefore, marking INVALID.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•