net/third_party/udt/doc/doc/t-error.htm - Issue 6708091: Remove UDT.

Unified Diff: net/third_party/udt/doc/doc/t-error.htm

Issue 6708091: Remove UDT. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/

Patch Set: Created 9 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Index: net/third_party/udt/doc/doc/t-error.htm

===================================================================

--- net/third_party/udt/doc/doc/t-error.htm (revision 78992)

+++ net/third_party/udt/doc/doc/t-error.htm (working copy)

@@ -1,48 +0,0 @@

-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

-<html xmlns="http://www.w3.org/1999/xhtml">

-<head>

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

-<title>Introduction</title>

-<link rel="stylesheet" href="udtdoc.css" type="text/css" />

-</head>

-<body>

-<div class="ref_head"> UDT Tutorial</div>

-<h3>Error Handling</h3>

-All UDT API will return an error upon a failed operation. Particularly, UDT defines UDT::INVALID_SOCK and UDT::ERROR as error returned values. Application should check the return

-value against these two constants (several routine return false as error value).

-On error, <a href="error.htm">getlasterror</a> can be used to retrieve the error information. In fact, the function returns the latest error occurred in the thread where the function is called. <a href="error.htm">getlasterror</a> returns an <a href="structure.htm">ERRORINFO</a> structure, it contains both the error code and special text error message. Two helper functions of <a href="structure.htm">getErrorCode</a> and <a href="structure.htm">getErrorMessage</a> can be used to read these

-information.

-The UDT error information is thread local (that is, an error in another thread will not affect the error information in the current thread). The returned value is a reference to the UDT internal error structure.

-Note that a successful call will NOT clear the error. Therefore, applications should use the return value of a UDT API to check the result of a UDT call. <a href="error.htm">getlasterror</a> only provides detailed information when necessary. However, application can use getlasterror().<a href="structure.htm">clear()</a> to clear the previously logged error if needed.

-Example: check UDT::bind error.

-<div class="code">

-sockaddr_in my_addr;

-my_addr.sin_family = AF_INET;

-my_addr.sin_port = htons(21); //invalid port number

-my_addr.sin_addr.s_addr = INADDR_ANY;

-memset(&(my_addr.sin_zero), '\0', 8);

-

-UDTSOCKET serv = UDT::socket(AF_INET, SOCK_STREAM, 0);

-if (UDT::ERROR == UDT::bind(serv, (sockaddr*)&my_addr, sizeof(my_addr)))

-{

-  cout << "bind: " << UDT::getlasterror().getErrorMessage();

-  // further action may depends on UDT::getlasterror().getErrorCode().

-  // system level error can be accessed through "errno"

-  return 0;

-</div>

-In the example above, the output will be:

-<div class="code">

-error message: Couldn't set up network connection: Permission denied.

-</div>

-The UDT error code only reflects the operation error of the UDT socket level. Applications can still read the system level error (e.g., errno in Linux, GetLastError in Windows) to read

-more specific error information. However, the error message obtained by getErrorMessage contains information of both the UDT level error and the system level error.

-

-</body>

-</html>

« no previous file with comments | « net/third_party/udt/doc/doc/t-data.htm ('k') | net/third_party/udt/doc/doc/t-file.htm » ('j') | no next file with comments »