Closed
Bug 18415
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] implement AsyncOpen for data protocol
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
INVALID
M13
People
(Reporter: warrensomebody, Assigned: jud)
References
Details
(Whiteboard: [PDT-])
In today's pork jockey meeting we determined that we must implement AsyncOpen
for all of our protocols in order to implement URL dispatching. This allows to
determine the content type of the incoming stream before determining the
recipient of the stream.
|
Reporter | |
Updated•25 years ago
|
Target Milestone: M12
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
|
|
Reporter | |
Updated•25 years ago
|
Target Milestone: M12 → M13
|
|
Reporter | |
Comment 2•25 years ago
|
||
We might be off the hook for this if I can convince mscott (and myself) that we
don't need it, and that a delegating stream listener would do the trick. Moving
to m13.
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
|
|
Assignee | |
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Comment 4•25 years ago
|
||
async open is going away
You need to log in
before you can comment on or make changes to this bug.
Description
•