On Mar 7, 2:14 pm, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > En Fri, 07 Mar 2008 04:16:42 -0200, <[EMAIL PROTECTED]> escribi�: > > > > > On Mar 7, 1:38 am, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > >> En Thu, 06 Mar 2008 14:34:27 -0200, <[EMAIL PROTECTED]> escribi�: > > >> > storage class which can write the file splits that are currently being > >> > downloaded to the disk. this is exactly what otherdownload > >> > accelerators do, i guess. > > >> Uh, unless I misundersand you, a standard file object is enough. First > >> create a file with the required size (open(...,'wb'), seek(n-1), > >> write(chr(0))). For each downloaded chunk you have to know its position > >> in > >> the file; then just seek() and write() it. > > > BUT the thing thats going in my mind is thread safety. i plan to start > > each part of the filedownloadin a different thread. and then when > > each thread had downloaded more than 100kb (or eof or boundary > > reached) write the buffer to the disk. can this be achieved using > > mutex ? i have never shared objects between threads. > > Use a different (single) thread to write the file; the others put write > requests on a Queue.queue object, and the writer just gets the requests > and processes them. > > > is there a way to write this without using threads at all ??? > > Using asyncore, and perhaps the Twisted framework. > > -- > Gabriel Genellina
asyncore is basically a server thing right? -- http://mail.python.org/mailman/listinfo/python-list
