#10147 closed enhancement (fixed)
Improve SimplePie memory usage
Reported by: | link92 | Owned by: | Denis-de-Bernardy |
---|---|---|---|
Milestone: | 2.8.1 | Priority: | normal |
Severity: | normal | Version: | 2.8 |
Component: | Performance | Keywords: | has-patch needs-review |
Focuses: | Cc: |
Description
Attachments (2)
Change History (14)
#3
@
15 years ago
- Keywords has-patch needs-review added
failed to find their revision log, for reference.
#6
follow-up:
↓ 8
@
15 years ago
Thanks. Out of curiosity, do you know why they're not using php's built-in parse_url() function?
http://bugs.simplepie.org/repositories/diff/sp1/trunk/simplepie.inc?rev=1036
#8
in reply to:
↑ 6
@
15 years ago
Replying to Denis-de-Bernardy:
Thanks. Out of curiosity, do you know why they're not using php's built-in parse_url() function?
http://bugs.simplepie.org/repositories/diff/sp1/trunk/simplepie.inc?rev=1036
We don't, because, uh… um, I wrote that code years ago? I think the answer is something along the lines of a few things in the manual:
- "Invalid characters are replaced by _." (This goes against what is needed for web compat.)
- "On seriously malformed URLs, parse_url() may return FALSE and emit a E_WARNING." (We want to break up everything before we try and make it valid, again for web compat.)
- "This function doesn't work with relative URLs." (Yeah, we parse those a lot, turning relative URIs into absolute ones.)
If the manual is wrong on all three things I'll remove our own parse_url. :)
#9
@
15 years ago
Also, the parse_url() function will go in SP 1.2 eventually, as everything will move over to the IRI class (actually, more likely the parse_url() will remain for backwards compatibility and just call the IRI class).
see #7652