I just ran your code on my device and simulator and it works as expected in both cases.
Use NSOperation instead of raw thread manipulation. It abstracts all sorts of stuff for you (priority, autoreleasepools etc...).? You can simply add some kind of delegate to your NSOperation subclass to get a callback when you need.
Thanks for replying so quickly! It turned out that the issue was not in this code fragment at all. I was executing this code dependent on a value in the keychain.
While my simulator's keychain has that value, my test iphone did not have this value. Feel so silly for troubling all of you. But following up on the reply from nduplessis helped me narrow down the issue.
You should update your question with this information, rather than putting it in an answer, so others won't try to answer. – Kristopher Johnson Mar 4 '09 at 22:23 done. Sorry newbie mistake – Naren Mar 4 '09 at 23:47 as Kristopher noted, you can update the original question and delete this answer.
– Can Berk Güder Mar 25 '09 at 9:55.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.