Necko: Difference between revisions

174 bytes added ,  18 October 2005
(sync http comments)
Line 12: Line 12:
* 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.
** Given that HTTP is largely a stream pump on top of a pipe, shouldn't this be much easier to do, by just exposing the input end more directly?
** Given that HTTP is largely a stream pump on top of a pipe, shouldn't this be much easier to do, by just exposing the input end more directly?
** Yes, we could do it that way.  However, there are issues to figure out such as whether or not blocking on a synchronous stream should block the UI from processing events.


* 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.
* 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.
272

edits