Re: [Libbt-devel] what's the typical use-case? [was: mess]

[Tyler M. <ty...@yi...>]

Alien <ali...@us...> wrote:
> > > - functions for converting peer communication into data structures
> i'd rather not, and instead supply a function that gives a the structure 
> that's already in memory

> > > - functions for converting peer responses from data structures into
> > > buffers * both communication of metadata and actual torrnent data
> i don't think this is necessary

	That's great if libbt is handling the actual connections, but that
might not always be the case.

> > > - functions for initiating connections to specific peers
> I'm not sure about this one

	It's neccessary for coding more intelligent connection handling; eg,
seeds preferring sharing with people with higher upload rates...

> wouldn't it be better if the library handled the torrent details, so that 
> frontends were easier to make?

	Depends on the frontend, I guess. :) The library should definately
provide handlers for the torrent details, but I would like it if the "dirty
work" wasn't *completely* concealed from the API...

	- Tyler