What is the hardest coding problem you ever tackled?
I've just completed my the hardest so far. It featured:
- Multi threading.
- More than one development language (Java/Javascript).
- Undocumented browser 'features'. And by undocumented, I mean Google appears not to have found any pages, anywhere, on the unique properties on iframes in IE. My documentation was a 10min chat with Alex last Javapolis. I have no idea where he found it out.
- More browser bugs than I want to remember.
- A lack of decent debugging resources.
The good news is that reverse Ajax in DWR now has fast efficient streaming working with Firefox and IE (Safari soon) using Jetty continuations. Thanks for TIBCO for sponsoring me to get this working, and to "Java Concurrency in Practice" for reminding me that multi-threading is hard, it's not just me being thick.
What's your toughest coding problem?
Re: What is the hardest coding problem you ever tackled?
My hardest coding problems have also generally involved either threading or things that are undocumented (for example, debugging problems in code for a socket protocol that I had no documentation for).
That is good news on the reverse Ajax front. I just started playing with the reverse Ajax support in 2.0.rc2 yesterday, and for the moment I switched to manually polling instead of using the reverse Ajax features due to the 30-second delay I was getting with Jetty. Is this likely to available soon in a new rc build?