Permalink
Browse files

Updating documentation links. Fixes issue #23

  • Loading branch information...
1 parent a56ced9 commit 5c28a2a23ab0ebf7fafbebe59e0f24de2f600177 @robbiehanson committed Feb 9, 2012
Showing with 11 additions and 13 deletions.
  1. +5 −6 GCD/Documentation.html
  2. +1 −1 RunLoop/AsyncUdpSocket.h
  3. +5 −6 RunLoop/Documentation.html
View
11 GCD/Documentation.html
@@ -5,19 +5,19 @@
<p>
A wealth of documentation can be found on the Google Code homepage:</br>
-<a href="http://code.google.com/p/cocoaasyncsocket/">http://code.google.com/p/cocoaasyncsocket/</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket">https://github.com/robbiehanson/CocoaAsyncSocket</a>
</p>
<p>
If you are new to networking, it is recommended you start by reading the Intro page:<br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/Intro">http://code.google.com/p/cocoaasyncsocket/wiki/Intro</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket/wiki/Intro">https://github.com/robbiehanson/CocoaAsyncSocket/wiki/Intro</a>
</p>
<p>
If you are a seasoned networking professional, with 10+ years of experience writing low-level socket code,
and detailed knowledge of the underlying BSD networking stack, then you can skip the CommonPitfalls page.<br/>
Otherwise, it should be considered mandatory reading:<br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/CommonPitfalls">http://code.google.com/p/cocoaasyncsocket/wiki/CommonPitfalls</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket/wiki/CommonPitfalls">https://github.com/robbiehanson/CocoaAsyncSocket/wiki/CommonPitfalls</a>
</p>
<h4>
@@ -26,12 +26,11 @@
</h4>
<p>
-The API reference page can be found here:</br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/Reference_GCDAsyncSocket">http://code.google.com/p/cocoaasyncsocket/wiki/Reference_GCDAsyncSocket</a>
+Your first goto for reference should ALWAYS be the header files. They are extremely well documented. Please read them.
</p>
<p>
-In addition to this, the headers are generally well documented.
+Did I mention you should read the headers? They're docemented very nicely, in plain english.
</p>
<p>
View
2 RunLoop/AsyncUdpSocket.h
@@ -19,7 +19,7 @@ extern NSString *const AsyncUdpSocketErrorDomain;
enum AsyncUdpSocketError
{
AsyncUdpSocketCFSocketError = kCFSocketError, // From CFSocketError enum
- AsyncUdpSocketNoError = 0, // Never used
+ AsyncUdpSocketNoError = 0, // Never used
AsyncUdpSocketBadParameter, // Used if given a bad parameter (such as an improper address)
AsyncUdpSocketIPv4Unavailable, // Used if you bind/connect using IPv6 only
AsyncUdpSocketIPv6Unavailable, // Used if you bind/connect using IPv4 only (or iPhone)
View
11 RunLoop/Documentation.html
@@ -5,19 +5,19 @@
<p>
A wealth of documentation can be found on the Google Code homepage:</br>
-<a href="http://code.google.com/p/cocoaasyncsocket/">http://code.google.com/p/cocoaasyncsocket/</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket">https://github.com/robbiehanson/CocoaAsyncSocket</a>
</p>
<p>
If you are new to networking, it is recommended you start by reading the Intro page:<br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/Intro">http://code.google.com/p/cocoaasyncsocket/wiki/Intro</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket/wiki/Intro">https://github.com/robbiehanson/CocoaAsyncSocket/wiki/Intro</a>
</p>
<p>
If you are a seasoned networking professional, with 10+ years of experience writing low-level socket code,
and detailed knowledge of the underlying BSD networking stack, then you can skip the CommonPitfalls page.<br/>
Otherwise, it should be considered mandatory reading:<br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/CommonPitfalls">http://code.google.com/p/cocoaasyncsocket/wiki/CommonPitfalls</a>
+<a href="https://github.com/robbiehanson/CocoaAsyncSocket/wiki/CommonPitfalls">https://github.com/robbiehanson/CocoaAsyncSocket/wiki/CommonPitfalls</a>
</p>
<h4>
@@ -26,12 +26,11 @@
</h4>
<p>
-The API reference page can be found here:</br/>
-<a href="http://code.google.com/p/cocoaasyncsocket/wiki/Reference_AsyncSocket">http://code.google.com/p/cocoaasyncsocket/wiki/Reference_AsyncSocket</a>
+Your first goto for reference should ALWAYS be the header files. They are extremely well documented. Please read them.
</p>
<p>
-In addition to this, the headers are generally well documented.
+Did I mention you should read the headers? They're docemented very nicely, in plain english.
</p>
<p>

0 comments on commit 5c28a2a

Please sign in to comment.