NetBurner Community Forum

rnixon wrote: ... task A could be writing data to the file, then task B is handed the file handle and starts writing as well, the data will be mixed will it not?

I apologize for omitting some detail. In my application, task A would pass the handle to task B after task A had finished using the handle.

pbreed wrote: I don't know the answer,
but could the task pass the file name instead and then there is no issue....

Until I know the answer, I think that's the direction I will be forced to take.

---------------
rnixon wrote: ... passing just the handle might have a problem. Have you tried it ...

Let's say I have 2 tasks, A and B. The file system has been initialized. Each of the tasks has called f_enterfs.

Task A opens a file, obtaining the file pointer/handle. Task A passes the file pointer/handle to task B.

Task B uses the file pointer/handle to perform some I/O, and then closes the ...

It's a c++ object, so maybe the fifo is freed when the destructor is called?

The netburner code shows fifos as a struct. Also OSFifoInit must be called explicitly
(instead of being included in a constructor), so I think it's a C object.

Are you talking about OS_FIFIO? I'm pretty sure that's ...

Are you unregistering the fifo before you exit?


Yes. But unregistering doesn't empty the fifo. It only breaks the
association with a port.

I have a question about pool buffer management.

Let's say that a function creates, initializes, and then registers a fifo for a UDP port.
The function then waits for incoming packets. Several packets arrive and are placed in
the fifo. The function removes one that it needed, with other packets ...

Has anyone had any experience implementing a proxy server (particularly a reverse proxy server) using Netburner ?