Necko: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 10: | Line 10: | ||
* Improve support for synchronous HTTP requests. This likely translates to an overhaul of the event queue system. | * Improve support for synchronous HTTP requests. This likely translates to an overhaul of the event queue system. | ||
* Support unicode file paths. This impacts the way we encode file URLs. Currently, we encode them in the "native filesystem charset" and then %-escape any non-ASCII bytes. This is not going to work if we wish to support full unicode file paths because the conversion from unicode to "native filesystem charset" may be lossy. | |||
Revision as of 17:41, 15 October 2005
TODO (for Gecko 1.9)
- Introduce nsBaseChannel from which other channels may subclass. This will help us consolidate duplicated code that is currently spread across each channel implementation and avoid inconsistencies in the process. It should also help reduce codesize a bit.
- Support IRIs better. This includes supporting %-escape sequences in hostnames. It also includes encoding non-ASCII URL parts to UTF-8, or more likely doing what other browsers do (which entails leaving the query parameters encoded in the origin charset).
- Introduce asynchronous authentication prompt API.
- Make it easier to use Necko from JS. This means use nsIClassInfo to automatically reflect interfaces, and it also means making it easier to work with streams from JS. nsIScriptableInputStream needs to be replaced with something better, for example.
- Improve support for synchronous HTTP requests. This likely translates to an overhaul of the event queue system.
- Support unicode file paths. This impacts the way we encode file URLs. Currently, we encode them in the "native filesystem charset" and then %-escape any non-ASCII bytes. This is not going to work if we wish to support full unicode file paths because the conversion from unicode to "native filesystem charset" may be lossy.