<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Persistent notes &#187; ace</title>
	<atom:link href="http://alexkr.com/tag/ace/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexkr.com</link>
	<description>Alexander Krivutsenko&#039;s online journal</description>
	<lastBuildDate>Sat, 07 Apr 2012 20:46:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Implementing shared counter with ACE</title>
		<link>http://alexkr.com/posts/146/implementing-shared-counter-with-ace/</link>
		<comments>http://alexkr.com/posts/146/implementing-shared-counter-with-ace/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 15:48:13 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[cpp]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/146/implementing-shared-counter-with-ace/</guid>
		<description><![CDATA[Recently I came across a specific issue while working with ACE_Atomic_Op on ACE build &#8220;5.4.6&#8243;.
The problem is that although ACE_Atomic_Op gives an access to the underlying synchronization object but still it is deprecated and causes deadlock.
ACE_Atomic_Op_Ex must be used instead.
Most probably it is specific to my configuration with Red Hat 3.2.3 (kernel 2.4.21) with ACE [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/146/implementing-shared-counter-with-ace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ACE_Reactor initialization</title>
		<link>http://alexkr.com/posts/139/ace_reactor-initialization/</link>
		<comments>http://alexkr.com/posts/139/ace_reactor-initialization/#comments</comments>
		<pubDate>Sat, 10 May 2008 14:46:54 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[cpp]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/139/ace_reactor-initialization/</guid>
		<description><![CDATA[I faced the problem when ACE_Reactor::run_reactor_event_loop() returned -1 with errno == 0.

This happened only on Linux while Windows code works pretty fine.

My ACE version is 5.4.6 and Linux is Red Hat with gcc 3.2.3

So as turns out that if ace reactor is used in its very default way:


   ACE_Reactor reactor;
    [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/139/ace_reactor-initialization/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Iterating a map in ACE</title>
		<link>http://alexkr.com/posts/138/iterating-a-map-in-ace/</link>
		<comments>http://alexkr.com/posts/138/iterating-a-map-in-ace/#comments</comments>
		<pubDate>Tue, 22 Apr 2008 16:55:05 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[cpp]]></category>
		<category><![CDATA[multithreading]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/138/iterating-a-map-in-ace/</guid>
		<description><![CDATA[STL containers are not thread safe but ACE containers support synchronization.
Consider you are using containers like std::map in multi threaded environment.
Normally there must be a critical section or a mutex which protects access to the container.
STL implementations do not provide such mechanism by default so C++ programmers must implement it.
ACE library has very flexible way [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/138/iterating-a-map-in-ace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ACE sleep on Linux and Windows</title>
		<link>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/</link>
		<comments>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/#comments</comments>
		<pubDate>Wed, 28 Feb 2007 16:06:51 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/programming/82/ace-sleep-on-linux-and-windows/</guid>
		<description><![CDATA[Today I found one significant difference in running ACE on Windows and Linux.
Consider the following statement:



 ACE_OS::sleep(0xFFFFFFF1);

 The effect is:

On Windows this will force the thread to sleep for 4294967281 seconds.

On Linux this command is processed immediately.


At this moment I don&#8217;t know why this happens.
I tried with value 0&#215;0FFFFFF1 on Linux and it went fine [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avoiding deadlocks with ACE_Reactor</title>
		<link>http://alexkr.com/posts/73/avoiding-deadlocks-with-ace_reactor/</link>
		<comments>http://alexkr.com/posts/73/avoiding-deadlocks-with-ace_reactor/#comments</comments>
		<pubDate>Wed, 10 Jan 2007 16:01:34 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[multithreading]]></category>

		<guid isPermaLink="false">http://alexkr.com/programming/73/avoiding-deadlocks-with-ace_reactor/</guid>
		<description><![CDATA[ACE_Reactor uses mutex to sync timer handling]]></description>
		<wfw:commentRss>http://alexkr.com/posts/73/avoiding-deadlocks-with-ace_reactor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

