Hello > Second, a correction is in order just to keep proprietary techno babble out: > - VfW was, and is, a proprietary format, i.e., some company owns it and > may change it whenever it wants to. It may even make it disappear and/or > prohibit you from further usage.
I totally aggree. Something like VfW is not a desired "standard" but one that you often just run into, if you look at existing video solutions. However, the trick with the intermediary client-application is that you put it inbetween your proprietary hardware (and most hardware is proprietary - video cards, digital cameras etc) and your free care2x server. Then you define a standard (protocol), how care2x wants to receive images. The client application simply translates from the proprietary hardware to the open and defined standrad that care2x sets. And for new hardware you may have to write a new client, but if it is open source, then it should not be a big deal And, unhappily though, I have to aggree with Alexander, that most workstations in hospitals are M$. Even if you install care2x on Linux, you will still find most users accessing it through a web browser on a M$ workstation. But unlike VfW, HTTP is an open standard, and thus care2x willl be available to M$ as long as they support HTTP. regards Kurt -- ---------------------------------------------------------------- Kurt Brauchli-Haase Telemedicine Unit, University of Transkei Umtata, South Africa tel: +27 47 502 2914 ---------------------------------------------------------------- ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
