Re: [Gaim-devel] Oscar FT update

[Christian H. <ch...@gn...>]

Off topic, but..

Got a question about your file transfer interface. I'm working on file
transfer for MSN, and MSN sends out little headers before each block
of data. The header is three bytes, and the 2nd and 3rd byte make up
the length of the data. So, the header is supposed to be read in and
then that number of bytes is supposed to be read in.

I'm not quite sure how to do this with the current API. It seems I can
setup a function that it will keep calling to do something with the
data, but I don't want to manually store the data in a buffer and
parse it myself. Maybe what I want can be done with the current API,
but I don't see how...

Basically, I need to be able to read in x amount of bytes, then say,
"Okay, you get 'y' many bytes and stick it in the file, and then call
me back when you're done and we'll continue this after I rest a bit."

Make sense? I hope so, because I'm not repeating it!

.. Unless it didn't make sense, in which case I'll say it again, only
differently.

Oh, and while I'm here... the fprintf and fscanf calls in ft_callback
seem... unnecessary. I'm tired, so please forgive any errors that may
cause an endless loop of kernel panics, but wouldn't these be better?

write(xfer->file, buf, rt);

and

read(xfer->file, buf, remain);

That would cut out the loops and the overly (for this case) expensive
calls to fprintf and fscanf.

And I want a puppy.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   "My brothers and sisters all hated me cause I was an only child."
      -- Weird Al Yankovich