Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change parser #91

Open
GoogleCodeExporter opened this issue Feb 7, 2016 · 4 comments
Open

change parser #91

GoogleCodeExporter opened this issue Feb 7, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

on iPhone 3GS, performance is ok
on other models, performance is not as good which is due to hardware
But the parser in use is too slow and memory intensive
is is possible to change this?

Original issue reported on code.google.com by [email protected] on 16 Mar 2010 at 5:52

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 17 Mar 2010 at 10:26

  • Added labels: Milestone-Release3.0

@GoogleCodeExporter
Copy link
Author

Hey Derek, how are you diagnosing the performance problem with the parser, and 
are
you talking about the XML parser, or something else?

Original comment by [email protected] on 29 Mar 2010 at 10:10

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

What parser is in question XML or or something else? Seems like pretty 
beneficial
application support feature to support equally well multiple versions of the
hardware. I do have to say the performance of the Imageshack app is worse than
twitter app for iPhone, when compared on 3GS hardware. The upload and load time 
is
slightly better or so it seems and application response time seems better. 
there are
sometime little delays navigating Imageshack app that not observed on twitter. 
Also
tweeter keeps the list of tweets locally which seems like a great feature as it 
only
need to update the list and not download it when I open and close app, like
Imageshack App. If no other Library dependent changes prove to be critical 
enough to
defer the release, defer implementation of this feature until next release. 

Original comment by [email protected] on 21 May 2010 at 8:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant