decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
P2P | 297 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
P2P
Authored by: Gringo_ on Monday, January 21 2013 @ 07:50 PM EST

I just completed making my own IPV4 peer-to-peer client and a simple little rendezvous server. It does UDP only, but I made a texting app for both my PC and my Android phone, and developed my own protocol to do reliable file transfer over (unreliable) UDP.

I know I have just reinvented the wheel here, but it has given me the greatest satisfaction to do that. The rendezvous server is so simple it can run on a consumer platform - it doesn't require Apache or anything like that. To connect P2P, a client contacts the server to get the addr/port of the other peer as seen by the server, then the two peers contact each other via NAT traversal. All the server needs is a port forwarded and a dynamic DNS service to make it visible to its clients. The peers run quite happily hidden behind firewalls and NATs, with no ports forwarded.

Thinking about the possibilities here gives me the greatest pleasure, like, I can text home from my phone to the PC, upload and download from it, control software running on the PC from the phone, etc.

I did it all on the PC side in C++ using the lowest level Winsock code, thereby the code I have should be easy to port to Linux when and if. On the phone, the peer is in Java, of course.

[ Reply to This | Parent | # ]

  • P2P - Authored by: JamesK on Monday, January 21 2013 @ 09:20 PM EST
Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )