> Doing a web-service call onthe UI thread should be ok if you intend the app > to block during the call? i.e. where the user is carrying out an action that > requires it to complete before they move on? >
Well, it would be "ok", but putting it into another thread is a lot better, as it gives you the option of doing things like allowing it to be cancelled, having animations or progress (eg "loaded 1 or 5" etc), which you will not easily get if it's all in the UI thread. If the whole app goes dark for 10 seconds, the user will assume it's died, and start blaming you. > I do this in my apps but I do suffer with the process hanging sometimes for > a long time and it happens inconsistently. I can't really allow them to run > on a new thread as I need the action to complete. I do this, and need to wait for the process to finish, in a couple of my apps. Works great :) Might be a different usecase tho. > > > > > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Webservice-no-internet-connection-tp3947219p3947508.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
