Re: [Gaim-devel] Oscar FT update

[Sean E. <se...@se...>]

I share Chip's concern.  When I first sat down to write the file
transfer GUI was the first time I looked at the API and I noticed this
right away.  Wouldn't it be better for the prpl to handle its sockets
itself and have its own callback which can strip headers and stuff and
then call a generic function with a pointer and a length?  That would
seem to be the optimal solution.

Apart from writing gtkcellrendererprogress, I've not started the file
transfer GUI--Rob may have started--either way changes to ft.c would not
interfere with it much, I'm sure.

-s.

On Sun, 2002-11-10 at 14:08, Ethan Blanton wrote:
> William T. Mahan spake unto us the following wisdom:
> > On Sun, Nov 10, 2002 at 03:14:37AM -0800, Christian Hammond wrote:
> > >
> > > 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."
> > 
> > You're right, there's no easy way to do that using the current API.  I
> > was hoping that no sane protocol would break up a file and send
> > headers in the middle, since it's not necessary over TCP.  Apparently
> > that was a bad assumption. :-(
> 
> ... But what if you want to interleave FT and other info on the same
> stream?  I can see this as being a very reasonable thing to do.
> 
> Ethan
> 
> -- 
> And if I claim to be a wise man / it surely means that I don't know.
>                 -- Kansas, "Carry on Wayward Son"