🚀 go-pugleaf

Morbideus:

If you have to write for hardware and can't fall to the standards that
exist for the device you would never get to Java as your language. 
That would be failing step 0 in starting the project.

The project (real time streaming video) you describe is done all over
the web already and it's a combination of Java and native code.  It is
possible to write portable native code, too.  It just takes a whole
heck of a lot of work!

For access to a serial port (parallel really wouldn't cut it for what
you describe), you can use the comm apis in Java (in beta) or any
number of in-expensive commercial products (I recommend SerialPort
from sc-systems.com) that have already done the work for a half dozen
hardware platforms for you.

-Rich

morbideus wrote:

> 
> The problem is when you want to create applications which communicate
> with hardware, and this is a common type of application:
> 
> For example I have a school project in java that is perhaps not
> feasible: a video+audio capture application from a camera that sends
> images in realtime on tcp/ip needs to read parallel or serial port and
> record wav from a sound card: It can be done but only whith APIs that
> are platform-specifics.
> 
> First the project had to be written in portable pure java, but I
> realize that it will not be so why would I continue wanting to use
> java for such a program ?

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=