Petrifying Horror on Twitter: "@mjtsai NSXMLDocument objects should be fine. It's parsers you don't want colliding."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Petrifying Horror ‏@boredzo 22 Aug 2014

PSA: Don't start a second NSXMLParser on the same thread where another NSXMLParser is already running, or you will have a bad time.
3 retweets 5 likes
Michael Tsai ‏@mjtsai 22 Aug 2014

@boredzo So all bets are off if you're using GCD and don't know the actual thread? Is NSXMLDocument safe?
Petrifying Horror ‏@boredzo 22 Aug 2014

@mjtsai You can use a serial queue, but not concurrent, for that reason. NSXMLDoc/Element: Probably the same story; haven't looked deeply.
Petrifying Horror ‏@boredzo 22 Aug 2014

@mjtsai Actually, concurrent may be fine. Not like GCD is going to call you twice at the same time on the same thread.
Michael Tsai ‏@mjtsai 22 Aug 2014

@boredzo I was thinking of long-lived objects (e.g. documents) that you call methods on.

‏@boredzo

@mjtsai NSXMLDocument objects should be fine. It's parsers you don't want colliding.

7:15 PM - 22 Aug 2014

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.