🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.soft-sys.khoros
Article #923

Re: Self-describing files (KHOROS mailing)

#923
From: George Huffman
Date: Wed, 16 Dec 1992 20:52
19 lines
1339 bytes
Brian - following up on our conversation, and this mail, the main barrier to
doing more with HDF from the Khoros viewpoint is time and $$$.  If the
Consortium members make it a priority it will happen; if not, it's a nice
idea that will accidently get done if it's easy or someone in the "community"
does it.  I'd guess that an interface to HDF isn't real hard for a hard-
core Khoros programmer, but otherwise, wading through the code would be
challenging.  

I wouldn't discount a "translator" approach; the data connections between
khoros programs can be implemented either as files (the default) or
through shared memory (mapped memory? it's the choice other than
"file" when you click on a connection in cantata).  So, the
translation program can be viewed as getting the data into memory with
minimal overhead for translating the header.

On the other hand, I exactly agree that Khoros will be more attractive
to NASA projects if HDF is "supported".  

George Huffman
Technical Details
Message-ID: <42200@pprg.eece.unm.edu.pprg.unm.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ncar!mimbres.cs.unm.edu!pprg.unm.edu!daemon

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ncar!mimbres.cs.unm.edu!pprg.unm.edu!daemon
From: huffman@donna.gsfc.nasa.gov (George Huffman)
Newsgroups: comp.soft-sys.khoros
Subject: Re: Self-describing files (KHOROS mailing)
Message-ID: <42200@pprg.eece.unm.edu.pprg.unm.edu>
Date: 16 Dec 92 20:52:30 GMT
Sender: daemon@pprg.unm.edu
Lines: 21