Re: libnjb 2.2.4 released

2005/10/10, Linus Walleij <[email protected]>:
> On Mon, 10 Oct 2005, Shaun Jackman wrote:
> > I think NJB_Get_Track_fd is a great addition to the API. How about
> > adding the equivalent NJB_Send_Track_fd?
>
> As discussed, the devices need the file length for transmitting metadata
> which is done before the actual file transmission occurs. When you send
> something from a file descriptor like a TCP socket or whatever you simply
> just don't know its size...
>
> It is probably possible to add this metadata ipso facto with an update
> after the descriptor reaches EOF, but must be experimented and tested
> with.

I see the difficulty with a pipe (or socket) where the eventual file
size is unknown. In my case though, the file descriptor points to a
temp file for which I have the fd and the file size, but not the file
name -- in fact, the name has probably already been unlinked. It would
help me out a lot if I could pass this fd to libnjb. Otherwise, I
first have to write the temp file to a second temp file, for which I
do know the name, and send that to libnjb. Not pretty.

With this framework in place, perhaps somebody else could then
contribute the work necessary to make the fd work with pipes and
sockets.

Cheers!
Shaun


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl