Re: miivi p2p protocol spec

From: Stefan Kaczmarek <stefan_at_thezonie.org>
Date: Fri, 11 May 2007 15:37:20 -0700

Uh, it's in the Google Doc thingy. For realsies.

Request File Chunk ("server") 0x20
Send File Chunk 0x11

Those are the messages you need to care about. You send the 0x20 and
get back the 0x11.

Each message exists in a single UDP packet. The message header is:

4 bytes Random int for encryption (not that we're doing this yet)
1 byte Op Code
2 bytes Data Length (this isn't really necessary, since the length
should be just what's in the datagram, but i think it's a good sanity
check.)

For op code 0x20, you'll just send the 20-bytes sha-1 hash after the
header, along with a long (8 byte) start and end file index. Then,
you will receive the 0x11 reply if they have the data, which they
should since they're publishing it. After the header will be the
sha-1, the start, the end, 2 bytes telling you what the file data
length is, and then the file data itself.

It's really freaking basic, pretty much because it's udp.

- Z

On May 11, 2007, at 3:06 PM, Ivan Kwok wrote:

> Iím sorry that I wasnít clear, what I meant was our miivi protocol
> for UDP file transfer.
>
>
>
> -Ivan
>
>
>
> From: Stefan Kaczmarek [mailto:stefan_at_thezonie.org]
> Sent: Friday, May 11, 2007 3:03 PM
> To: Ivan Kwok
> Cc: Jay Mairs
> Subject: Re: miivi p2p protocol spec
>
>
>
> Just look at the Google Document thingy. It's complete and up-to-date.
>
>
>
> Let me know if you have any questions about it.
>
>
>
> - Z
>
>
>
> On May 11, 2007, at 2:06 PM, Ivan Kwok wrote:
>
>
>
>
> Hi Stefan, can you give me the detail of UDP protocol
> specification? I am writing a native server app for publishing.
>
>
>
> Thanks,
>
> -Ivan
>
>
>
>
>
>
>
>
>
Received on Fri Sep 14 2007 - 10:56:02 BST

This archive was generated by hypermail 2.2.0 : Sun Sep 16 2007 - 22:19:48 BST