One of the hardest types of bugs to track down is a deadlock situation. They are very time dependant which makes them intermitten, specific to a particular computer and configuration and generally impossible to reproduce in a debugger. Fortunately, at least in Java, it’s fairly easy to spot most of the situations where a deadlock is possible:
Here is some great news for Nokia S60 users, apparently Nokia has been working on revamping the security framework on Java applications and the nagging permissions we continuously need to give in order for them to work, may soon be a thing of the past. The idea behind prompts was security but since native applications and other runtime applications do not have to follow the same rules on S60, Nokia’s decided to rid Java applications of the burden too. We can finally hope to check our Gmail without hitting ‘Yes’!
The two things that should make the situation better for Java developers on S60:
Since the search function for Apple’s mailing lists is pretty much useless, I’m making a note of the Reading PICT Images thread which contains numerous options for rendering PICT images in Java on OS X.
If your application uses java.net.URL, and chances it does are very high, and you are using Sun's JVM (since 1.4.2), you should set the sun.net.client.defaultConnectTimeout and sun.net.client.defaultReadTimeout system properties to a reasonable value. Otherwise, if a remote site hangs, your application or server will also hang.
Useful to know…
Gli amici di BlackBerryItalia segnalano sul sito di IQ-mobile la disponibilià di programmi e giochi gratuiti per palmari Java tra cui anche i BlackBerry RIM..
clicca qui per maggiori informazioni
Following recent moves to extend Skype™ conversations to a wide variety of new mobile and wireless devices, Skype is taking another major step as it continues to merge its internet communications software with mobile phones. Today, the company released a beta version of Skype for your mobile, a mobile “thin“ client that works on about [...]