Grr

[mdlbear]

As it turns out, PalmOS doesn't multitask. So as long as Java (i.e., the web server) is running, you can't run the browser. An vice versa. So it'll make a pretty decent server demo, but not nearly as effective as it could have been, and completely useless as a practical matter.

Why am I not surprised?

Comments

Ah, the fun of porting to PalmOS

[filker0.livejournal.com]

I believe you'd also find that, because PalmOS is designed to do as little as possible in order to save power, a web server running on a Palm may discover all sorts of problems with waiting on an IP port, or more specifically, waking up when something connects (or attempts to connect) with the port.

Of course, I could be completely wrong. My PalmOS network programming book is at home, and I'm not.

[madfilkentist]

I'm reminded of Java development under the old Mac OS. According to the Java specification, you should assume all threads may run until they explicitly yield. This assumption is necessary on OS's which don't have preemptive multitasking, such as old Mac OS and Palm OS, but a lot of real-life Java software expects preemptive multitasking and will hang on such OS's.