[Twisted-Python] Large file transfers

Steve Waterbury steve.waterbury at gsfc.nasa.gov
Thu Jul 25 14:43:33 MDT 2002


Glyph Lefkowitz wrote:

> There will be a little bit of overhead in the initial implementation,
> considering that it will be using PB calls.  In the short term, the large file
> transfers would probably be better handled over HTTP (Twisted's
> twisted.web.static.File can easily be used to this end).  FTP is a much nastier
> protocol.

Ah, my ignorance again -- I hadn't noticed twisted.web.static.File;  
I'll look at that ... we'll be doing at least 3 interfaces that use 
HTTP anyway (web, xmlrpc, and SOAP) ... thanks!

> > is anyone working on / contemplating a CL implementation of PB?  :^)
> 
> We have contemplated it a lot, but have yet to implement it.  Really the
> problem is that "common lisp" isn't a language so much as a bizarre
> constellation of languages, none of which have anything to do with each other
> when it comes to things like "sockets" and "files".  It hasn't been worth
> anybody's effort to go to all that work just for, say, CLisp or SBCL.  AFAIK
> it's not even *possible* to do it properly in CLisp yet, due to the absence of
> non-blocking sockets, but this could be FUD; haven't read the docs in a while.
> 
> However, many of us are fans of Lisp-like languages and I'm sure that more than
> one person would be thrilled to see a multi-vendor-supporting CL
> implementation of PB.

Yeah, the non-blocking sockets might be a problem ... I'll ask about 
that.  If we do an implementation, we'll at least make an effort to 
make it multi-vendor-supporting.  Our Lisp specialists have used both 
Allegro and Harlequin at various times.  Let us know if other vendor 
or open-source Lisps are of interest, etc.  

Cheers,
-- Steve.

Stephen C. Waterbury  http://misspiggy.gsfc.nasa.gov/people/waterbug.html




More information about the Twisted-Python mailing list