Hi,
I want to show you my latest work done in processing....
Recently I have been in continuous contact with my friends in Japan, who are all living in Tokyo. Fortunately, they are all fine. The big Sendai earthquake and the following tsunami did not harm them directly. But - besides the nuclear danger - there are many aftershocks happening all the time. A friend told me that Tokyo feels like pudding, another one told me on saturday that the earth is shaking every 30 minutes, and earthquakes are regularly occurring in the middle of skype conversations. For me, and especially for my friends in Japan this is a tremendous psychological challenge - even if those earthquakes are not as strong as the big one. But you never know…
Well, yesterday night this led me to the idea of trying to visualize that feeling - a timelapse of 5+ earthquakes from the past 7 days. What you see is a screencapture of a program that I wrote overnight. Thanks to the XML feed of the US Geological Survey, the program is running live and updates automatically.
Many thanks go to Mahir M. Yavuz, Ritornell and mimu merz for their immediate help and support.
If there are no new messages for a while there is a SocketTimeoutException. and after that the library is waiting for some time to reconnect (sleeping time).
reconnect failed. sleeping for 1000 ms before attempting next reconnect
1000ms would be no problem, but if there's no new tweet coming in for some time the sleeping time automatically adds up to a long time to reconnect.
well what i want to achieve is that my app checks twitter continuously (at least something like every 2 seconds on a regular base). i think i have to control either the socketTimeoutMs so it stays connected longer or i should get control of the increasing sleeping time.
i tried
s.socketTimeoutMs = 200000;
throws an error
The field TweetStream.socketTimeOutMs is not visible
