comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Re: Non-Blocking I/O

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Non-Blocking I/O [message #14297 is a reply to message #14291]

Fri, 12 February 1999 00:00

Ruediger Kupper
Messages: 7
Registered: February 1999

Junior Member

William Thompson wrote in response to ashmall@my-dejanews.com (Justin Ashmall):

>> Just a thought, but would an FSTAT on the unit number give you any information
>> as to whether there was data waiting to be read?
>
>> Justin
>
> Probably not. I've dealt with situations where we've had to read from a file
> which was open for write by another process. As I recall, the behavior of
> FSTAT was somewhat flakey under those conditions.

Exactly. FSTAT -seems- to be just the IDL function that should do the job, but
unfortunately it gives absolutely no hint in this case.
FSTAT results do look like

** Structure FSTAT, 12 tags, length=36:
UNIT LONG 100
NAME STRING '/homes/kupper/IPC/fifo'
OPEN BYTE 1
ISATTY BYTE 0
ISAGUI BYTE 0
INTERACTIVE BYTE 0
READ BYTE 1
WRITE BYTE 0
TRANSFER_COUNT LONG 1
CUR_PTR LONG -1
SIZE LONG 0
REC_LEN LONG 0

regardless of any waiting or not waiting data.

Good thought Justin, anyway!

> The situation we were dealing with was to read an incoming spacecraft telemetry
> stream. Since there already was a process (written in C) which was archiving
> the telemetry stream into data files, what we ended up doing was to simply read
> those files while they were still being written. That way, we avoided the
> whole pipe/fifo business. Sounds like that wouldn't help you, though.
>
> Our original scheme was to use a two-way socket connection between IDL and a C
> process which was handling telemetry reception. IDL would send out a request
> for data to the socket, and the C process would either respond with a
> packet, or with a "no-data-yet" message. That way, IDL would always read back
> something.

Okay, so there seems to be no way around using some intermediary C-Routines which
handle reception.
IDL just doesn't support Inter Process Communication...

Thank you both for your help.

Best regards,
Ruediger.

Report message to a moderator

[Message index]

		Re: Non-Blocking I/O By: korpela on Tue, 16 February 1999 00:00
		Re: Non-Blocking I/O By: davidf on Mon, 15 February 1999 00:00
		Re: Non-Blocking I/O By: menakkis on Mon, 15 February 1999 00:00
		Re: Non-Blocking I/O By: ashmall on Sat, 13 February 1999 00:00
		Re: Non-Blocking I/O By: Ruediger Kupper on Fri, 12 February 1999 00:00
		Re: Non-Blocking I/O By: thompson on Thu, 11 February 1999 00:00
		Re: Non-Blocking I/O By: ashmall on Thu, 11 February 1999 00:00

Previous Topic:	Setting IDLgrPolyline vertex colours?
Next Topic:	Non-Blocking I/O

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 12:09:31 PDT 2025

Total time taken to generate the page: 0.32175 seconds