Closed Bug 106069 Opened 23 years ago Closed 22 years ago

FTP should be in the core necko lib.

Categories

(Core Graveyard :: Networking: FTP, defect, P3)

Product:
Core Graveyard
Component:
Networking: FTP
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Future

People

(Reporter: jud, Assigned: darin.moz)

References

Details

(Keywords: embed, memory-footprint, topembed+) 

Currently FTP is built and linked into the necko2 lib (secondary) for
factorying/dist reasons. However, now that time has passed from this initial
decision, we're finding that enough websites include "<img src='ftp://...'>"
tags which require FTP to be around anyway. We should link FTP into the core
necko lib.
Also see bug 98753.

Since the changes for this bug are really simple (just move some stuff from
build2 to build), I think that it would be easier for someone with a mac to do
it. darin?
sure... i'll try to do this sometime before moz 1.0 ... probably when i get
around to working on cleaning up CID/ContractID definitions and other
outstanding public necko api issues.
Assignee: bbaetz → darin
Priority: -- → P3
Target Milestone: --- → mozilla0.9.8
adding footprint keyword. this is causing embeddors to drag in necko2 when they
don't need to.
Keywords: footprint
valeski: please help me set a milestone for this... how important is this?
-> mozilla1.0
Status: NEW → ASSIGNED
Keywords: mozilla1.0
Target Milestone: mozilla0.9.8 → mozilla1.0
jud: is this topembed?
yea, let's whack this in.
Keywords: topembed+
jud: actually, does it really make sense to do this?  necko2.dll isn't loaded at
startup, but necko.dll is.  if we move FTP intl necko.dll, then we'll be loading
it at startup.  isn't this going against the goal of trimming startup fat?

see also bug 106206, which wants to move the data and keyword handlers into
necko2.dll.

i'm tempted to mark this WONTFIX.
when talking about memory/disk footprint and performance, there are many goals
that are conflicting. 

IMO, it would be better to take the incremental hit (I can't imagine it's
perceivable) of adding the FTP code loading overhead to necko.dll, rather than
pushing a completely separate shared lib around (necko2.dll).
post 1.0
Target Milestone: mozilla1.0 → mozilla1.0.1
removing topembed+ and adding embed since darin made a comment that this would
be done post 1.0.
Keywords: topembed+ → embed
Target Milestone: mozilla1.0.1 → ---
mass futuring of untargeted bugs
Target Milestone: --- → Future
batch: adding topembed per Gecko2 document
http://rocknroll.mcom.com/users/marek/publish/Gecko/Gecko2Tasks.html
Keywords: topembed
Keywords: topembed → topembed+
Blocks: grouper
alec just fixed this as part of another bug. alec, can you provide the bug
number for record keeping?
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
it was bug 170987 (we could also mark this a dupe of that)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.