trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1079641 - in /trafficserver/site/branches/ats-cms/content/docs/trunk/sdk: actions-guide/order.txt mutex-guide/index.en.mdtext
Date Wed, 09 Mar 2011 02:12:20 GMT
Author: igalic
Date: Wed Mar  9 02:12:19 2011
New Revision: 1079641

URL: http://svn.apache.org/viewvc?rev=1079641&view=rev
Log:
Adding another order file
Fixing minor style issue

Added:
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/order.txt
Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext

Added: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/order.txt
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/order.txt?rev=1079641&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/order.txt (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/order.txt Wed
Mar  9 02:12:19 2011
@@ -0,0 +1,2 @@
+index
+hosts-lookup-api

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext?rev=1079641&r1=1079640&r2=1079641&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext
Wed Mar  9 02:12:19 2011
@@ -41,7 +41,7 @@ a variable and/or use atomic operations.
 other than the one recommended above, then the result will be a serious performance 
 impact. 
 
-`**TSMutexLockTry**`, on the other hand, attempts to lock the mutex only if 
+**`TSMutexLockTry`**, on the other hand, attempts to lock the mutex only if 
 it is unlocked (i.e., not being used by another thread). It should be used 
 in all cases other than the above mentioned `TSMutexLock` case. If the `TSMutexLockTry` 
 attempt fails, then you can schedule a future attempt (which must be at least 



Mime
View raw message