Open Bug 1352012 Opened 7 years ago Updated 2 years ago

Use a separate read-only connection for favicon protocols

Categories

(Toolkit :: Places, enhancement, P3)

Product:
Toolkit
Component:
Places
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: mak, Unassigned)

References

Details

(Whiteboard: [fxsearch]) 

There's no reason to use the main connection to serve protocol requests, we should probably split a separate and concurrent connection.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.