Open GoogleCodeExporter opened 9 years ago
If a change in paths would break compatibility (require migration on upgrade
code)
can we fix the crazy long path components with spaces too?
"Google Gears for Internet Explorer"
"Google Gears for Firefox"
Original comment by linus.up...@gmail.com
on 11 Jun 2007 at 3:19
Might also be an opportunity to use fewer special characters in names. Right
now we
have _ as the separator for protocol/port (ex: "http_80"), # as the suffix
separator
(ex: dbname#database), and [] used in versioning (ex: "file[12].html").
Bringing it
all together, you get paths like:
www.myapp.com/http_80/mystore_managed[29]#localserver/myfile[12].html
Both the # and [] are definitely not the greatest for Unix-based systems,
though most
shells handle them pretty well these days (auto-complete will usually
auto-escape).
But Gears should NEVER use any filesystem manipulation code which hasn't been
thoroughly vetted for globbing or other shell interpretation. These could also
cause
porting issues, insofar as systems inject their own understanding of magical
characters.
Original comment by Scott.Hess
on 11 Jun 2007 at 5:48
Original comment by gears.te...@gmail.com
on 27 Jun 2007 at 7:24
Original comment by gears.te...@gmail.com
on 2 Jul 2007 at 6:59
Original comment by gears.te...@gmail.com
on 5 Sep 2007 at 12:10
Original comment by gears.te...@gmail.com
on 5 Sep 2007 at 4:41
Original issue reported on code.google.com by
Scott.Hess
on 9 Jun 2007 at 12:06