Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #37980 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2013-01-31 15:32 +1100 |
| Last post | 2013-01-31 15:32 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: pyrudp Chris Angelico <rosuav@gmail.com> - 2013-01-31 15:32 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2013-01-31 15:32 +1100 |
| Subject | Re: pyrudp |
| Message-ID | <mailman.1242.1359606765.2939.python-list@python.org> |
On Thu, Jan 31, 2013 at 3:26 PM, <wrw@mac.com> wrote:
> Now, the good news is that because UDP-based protocols all run in user memory space (as opposed to TCP that runs privileged in kernel space) it is relatively straightforward for non-privledged users to write and test UDP transport schemes and this has become a fairly standard CS exercise at the graduate level. If I were in your shoes, I'd start Googling for the papers published on protocols like HURRICANE, ATAU, or even just the general subject of UDP transport protocols.
I'd still include reading up on TCP. The RFC has a good bit about why
things are the way they are; when you're designing a protocol that
does similar things, it's worth getting an understanding of what your
predecessors did. Either you'll get some ideas ("yeah, that's how I'll
do it!") or you'll decide you can do better, but it's still worth a
read.
ChrisA
Back to top | Article view | comp.lang.python
csiph-web