Re: [Python-Dev] r64407 - python/trunk/Doc/library/multiprocessing.rst
On Jun 20, 2008, at 5:46 PM, Steve Holden wrote: Perhaps we need a split between "networking technologies" and "network-based applications". Perhaps that would help. I certainly see HTTP as being on the same layer as SMTP and the like, but application protocols that ride on top of HTTP are a different beast. -Fred -- Fred Drake ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r64407 - python/trunk/Doc/library/multiprocessing.rst
A.M. Kuchling wrote: On Fri, Jun 20, 2008 at 08:55:13AM -0700, Bill Janssen wrote: Is anyone else finding it increasingly odd that subprocess, signal, socket/ssl, and syncore are in the same chapter? I'm tempted to move socket, ssl, asyncore+asynchat into a 'networking' chapter, and then also move SocketServer from the 'Internet Protocols' chapter into this new chapter. Sounds like you mean, 'Non-HTTP Networking'. I don't think so -- SMTP, FTP, NNTP, and telnet have nothing to do with HTTP, but they're certainly Internet protocols. Perhaps we need a split between "networking technologies" and "network-based applications". regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r64407 - python/trunk/Doc/library/multiprocessing.rst
> On Fri, Jun 20, 2008 at 08:55:13AM -0700, Bill Janssen wrote: > > > Is anyone else finding it increasingly odd that subprocess, signal, > > > socket/ssl, and syncore are in the same chapter? I'm tempted to move > > > socket, ssl, asyncore+asynchat into a 'networking' chapter, and then > > > also move SocketServer from the 'Internet Protocols' chapter into this > > > new chapter. > > > > Sounds like you mean, 'Non-HTTP Networking'. > > I don't think so -- SMTP, FTP, NNTP, and telnet have nothing > to do with HTTP, but they're certainly Internet protocols. Sure, but there's typically only one protocol that's carried over any of them. Whereas with REST and XML-RPC and so forth, there's a whole cottage industry of using HTTP as a carrier, in much the same way that TCP is used at a lower level. But you're right: there's "Networking / Generic Support", "Networking / Specific Protocols", and "Networking / HTTP-based", or some such. Bill ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r64407 - python/trunk/Doc/library/multiprocessing.rst
On Fri, Jun 20, 2008 at 08:55:13AM -0700, Bill Janssen wrote: > > Is anyone else finding it increasingly odd that subprocess, signal, > > socket/ssl, and syncore are in the same chapter? I'm tempted to move > > socket, ssl, asyncore+asynchat into a 'networking' chapter, and then > > also move SocketServer from the 'Internet Protocols' chapter into this > > new chapter. > > Sounds like you mean, 'Non-HTTP Networking'. I don't think so -- SMTP, FTP, NNTP, and telnet have nothing to do with HTTP, but they're certainly Internet protocols. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
