[DOGFOOD] implement AsyncOpen for keyword protocol

VERIFIED INVALID

Status

()

Core
Networking
P3
normal
VERIFIED INVALID
19 years ago
18 years ago

People

(Reporter: Warren Harris, Assigned: Judson Valeski)

Tracking

Trunk
All
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PDT-])

(Reporter)

Description

19 years ago
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

19 years ago
Depends on: 14928
(Reporter)

Updated

19 years ago
No longer depends on: 14928
(Reporter)

Updated

19 years ago
Blocks: 14928
(Reporter)

Updated

19 years ago
Target Milestone: M12

Updated

19 years ago
Whiteboard: [PDT-]

Comment 1

19 years ago
Putting on PDT- radar.  Porkjockey work.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
(Reporter)

Comment 2

18 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.
Target Milestone: M12 → M13

Comment 3

18 years ago
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
(Assignee)

Comment 4

18 years ago
async open is going away

Comment 5

18 years ago
verified invalid
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.