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

Ti.meteor uses tiws and has problems with tiws #14

Closed
AppWerft opened this issue Jan 15, 2015 · 7 comments
Closed

Ti.meteor uses tiws and has problems with tiws #14

AppWerft opened this issue Jan 15, 2015 · 7 comments

Comments

@AppWerft
Copy link
Contributor

Hi Oliver,

currently I'm playing with Ti.Meteor. In the issue tracker (moritzknecht/TiMeteor#2) I found stories about crashes on iOS. Moritz wrote about PocketSockets and the crashes disappears …… What do you think about crashes and the alternative?

Rainer

@omorandi
Copy link
Owner

@AppWerft I think it would be cool having some more info about those crashes ;-)

@AppWerft
Copy link
Contributor Author

@omorandi After a little workshop about TiMeteor we think the module is a little immature. The original meteor libs are copied into the module. I think I would copied copy all new versions. It seems to be unsustainable and fragmented. On the other hand: Meteor is great! Thanks for your answer.

@omorandi
Copy link
Owner

Ok, closing this for now

@icellan
Copy link

icellan commented Jan 19, 2015

@omorandi @AppWerft I have been using the tiws websocket implementation for some time in my Titanium projects and it has never been 100% stable (version 0.5 by @omorandi is the most stable). The apps have always been plagued by crashes. Granted they have all been talking to a Meteor backend, but I have used multiple implementation on the Titanium Javascript end.

When I replaced tiws with a native Javascript implementation, the crashes did not occur anymore, but this introduced other problems, like no support for large data (images) to be transported over the websocket.

The problems with twis seem to occur mostly when the app is brought back from sleep. So my hunch is that it has something to do with state and unexpected info coming from the server.

@yuchi
Copy link

yuchi commented Jan 19, 2015

Can you create a list of issues for your instability? I’d like to set up automated tests so step to reproduce and expected/actual results could help me.

I don’t know how to test the when the app goes to the bg and back to the fg…

@omorandi
Copy link
Owner

Yes, I'd be happy to review any crash log hinting that issues come from tiws, but without any (or even minimal steps to reproduce), it's difficult to help.
My aim is to to try to make TiWS a solid, standards-compliant websocket implementation for Ti. In the mid-long term I'm seeing Socket.io, or any other dependent library, being removed from this repository.
@yuchi, wrt automated testing, I started thinking about that too (see also #16). Let's sync on this

@icellan
Copy link

icellan commented Jan 23, 2015

I've been trying to recreate this issue for a crash log, but have not been able to do that yet (which is a good thing). I have checked with our users and it looks like we have not been getting any crash reports either in the last couple of weeks.

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

No branches or pull requests

4 participants