|
It seems like option 2 is the best (though I am not real fond of doing my own thread programming). Are there other methods that I could use that would also be good to consider?
Why not?
Well, let's just say my first big project on threads made my head ache all over the place. I wrote a J2ME application for a Canon MFD (Multi Functional Device) and had to work with the low level hardware API's (basically a program written in C wrapped by Java). I learned a lot, but mostly learned to shudder at the sound of threads :-) I must say that I don't feel I have "mastered" threads though I have used them a lot. If anybody has an example of reading a data queue entry and then spawning a thread that writes some info to a secondary data queue I would be much appreciative :-) Though this definitely has given me more insight as to how everything is organized within a job after reading a lot of the beginning segments in the following url: http://tinyurl.com/bfaad Aaron Bartell http://mowyourlawn.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.