Closed Bug 19292 Opened 25 years ago Closed 20 years ago

Need two DDE Calls implemented

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED WONTFIX
Milestone:
Future

People

(Reporter: mikepinkerton, Assigned: law)

References

Details

(Whiteboard: [nsbeta2-][nsbeta3-]) 

External developers need the WWW_RegisterProtocol and WWW_UnRegisterProtocol DDE
calls implemented by the time we ship.

You can come talk to me for details.
Do we still need this? Mscott should evaluate for url dispatching.
Target Milestone: M13
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
Target Milestone: M13 → M14
let get this figured out and kill the bug if no longer needed.
->m14
yes, this is still needed.
Clearly this is not blocking the stability of the M15 checkpoint...
...so I'm pushing it to M16 to facilitate the M15 branch.
Target Milestone: M14 → M16
reassigning jevering's old bugs to jar for adoption or to
find them a new home
Assignee: jevering → jar
Pink,

Please re-assign this to the person that you think *should* be handling this issue.

Thanks,
Jim
Assignee: jar → pinkerton
Um, i have no idea. You're the manager ;)
Assignee: pinkerton → jar
The bouncing of the bug continues....
I'm passing this to Warren who will probably pass this down into his
organization till it finds a home.
Assignee: jar → warren
Is this needed for beta2?

David: Do you know how to implement these?
Nope although I am sure I could look it up. But this sounds like platform 
integration work so I say reassign it to don;)

Don: Do you have someone that can implement this?
Assigning to Don.
Assignee: warren → don
Reassigning for Don
Assignee: don → law
Keywords: nsbeta2
who is asking for this, what's the business case? how critical is it? how hard 
is this to implement? marking nsbeta2+
Whiteboard: [nsbeta2+] 5/16
I dunno about any of those questions save the last.  I am in the process of 
landing a simplistic DDE handler.  This will give us a place to put code to 
handle those particular DDE requests (that part would be trivial).

The harder part is actually routing requests to the DDE servers so registered.  
That requires wiring something into the URI dispatcher, I reckon.  Not sure how 
easy that would be (mscott would know better).  Also, I'm not sure exactly how 
those requests get routed.  We likely would need some more code to do that (and, 
it would appear to use some DDE mechanism that isn't implemented/exposed).
the contact person for this bug is:
thomasvl@aol.com

AOL needs it by the time we ship final bits, but it is not required for beta2

Move to M19.
Target Milestone: M16 → M19
Need info on who needs this for RTM.
Whiteboard: [nsbeta2+] 5/16 → [NEED INFO]
Putting on [nsbeta2-] radar.   sol to follow up.
Whiteboard: [NEED INFO] → [nsbeta2-]
Sent email to thomasvl@aol.com to determine if this fix is still needed and, if 
so, when it's needed.

I will follow up in the bug when I have a response.


Move to M20 with the rest of the "nsbeta-" bugs.
Target Milestone: M19 → M20
Bill thinks this will take about a week to implement.
Status: NEW → ASSIGNED
Nav triage team: [nsbeta3-]
Blocks: 25699
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so 
the queries don't get all screwed up.
Keywords: nsbeta3
mass move, v2.
qa to me.
QA Contact: tever → benc
Setting target milestone.  I don't think this is top priority, perhaps not even
tops amongst the possible DDE features.
Target Milestone: --- → Future
i'm happy to wontfix this.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
V/wontfix.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.