<?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>ResoMail blog</title>
	<atom:link href="http://blog.resomail.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.resomail.com</link>
	<description>ResoMail secure cryptographic mail</description>
	<lastBuildDate>Sat, 19 Dec 2009 21:49:30 +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>Java bytecode decompiler</title>
		<link>http://blog.resomail.com/2009/12/java-bytecode-decompiler/</link>
		<comments>http://blog.resomail.com/2009/12/java-bytecode-decompiler/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 21:49:30 +0000</pubDate>
		<dc:creator>sergio</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.resomail.com/?p=34</guid>
		<description><![CDATA[A bytecode decompile is a tool which usually is seldom needed but when needed you would want to have it handy. There seems to be a lot of time since I&#8217;ve used one and when I needed one now I didn&#8217;t know what to choose, there are a lot outdated ones, which don&#8217;t decompile Java [...]]]></description>
			<content:encoded><![CDATA[<p>A bytecode decompile is a tool which usually is seldom needed but when needed you would want to have it handy. There seems to be a lot of time since I&#8217;ve used one and when I needed one now I didn&#8217;t know what to choose, there are a lot outdated ones, which don&#8217;t decompile Java 1.5 correctly.<br />
After a web search I&#8217;ve found <a href="http://java.decompiler.free.fr/">Java Decompiler</a> which has even a GUI and is quite good.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.resomail.com/2009/12/java-bytecode-decompiler/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Debugging Java Concurency bugs</title>
		<link>http://blog.resomail.com/2009/07/debugging-java-concurency-bugs/</link>
		<comments>http://blog.resomail.com/2009/07/debugging-java-concurency-bugs/#comments</comments>
		<pubDate>Sun, 19 Jul 2009 12:09:59 +0000</pubDate>
		<dc:creator>sergio</dc:creator>
				<category><![CDATA[Java development]]></category>
		<category><![CDATA[concurrency]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[java]]></category>

		<guid isPermaLink="false">http://blog.resomail.com/?p=24</guid>
		<description><![CDATA[We recently had a nasty concurrency bug in our server software, it was a data corruption bug. And I&#8217;ll try share the experience of debugging it:

1. First of all you&#8217;ll need to reproduce this bug. With concurrency bugs it&#8217;s not that easy, you&#8217;ll have to create test scripts which try to reproduce the bug, ideally [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0in;">We recently had a nasty concurrency bug in our server software, it was a data corruption bug. And I&#8217;ll try share the experience of debugging it:</p>
<p style="margin-bottom: 0in;">
<p style="margin-bottom: 0in;">1. First of all you&#8217;ll need to reproduce this bug. With concurrency bugs it&#8217;s not that easy, you&#8217;ll have to create test scripts which try to reproduce the bug, ideally it should be one click script and reproducibility 100% or close. If you don&#8217;t have 100% reproducibility try to add more threads or less, more data or more time/times running your code.</p>
<p style="margin-bottom: 0in;">
<p style="margin-bottom: 0in;">2. Localization of your bug. Here you&#8217;ll need a good logging solution, which can log events from concurrent threads. You should identify each log entry by it&#8217;s thread, if thread has some human readable identifier &#8211;  it&#8217;s great (we had ResoMail identifiers for each thread)</p>
<p style="margin-bottom: 0in;">
<p style="margin-bottom: 0in;">3. Review the code you&#8217;ve localized, look for any static or shared non final data, ideally there should be none. Be careful about final objects which have internal state, the object internal state might not be final &#8211; if you&#8217;re in doubt try unsharing the object, for example transform it from static to dynamic  or clone the objects and see how it works.</p>
<p style="margin-bottom: 0in;">
<p>Recommended reading:   <a title="Java Concurrency in Practice" href="http://jcip.net" target="_blank">Java Concurrency in Practice</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.resomail.com/2009/07/debugging-java-concurency-bugs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing started</title>
		<link>http://blog.resomail.com/2009/06/testing-started/</link>
		<comments>http://blog.resomail.com/2009/06/testing-started/#comments</comments>
		<pubDate>Sun, 28 Jun 2009 05:47:09 +0000</pubDate>
		<dc:creator>sergio</dc:creator>
				<category><![CDATA[ResoMail]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[private]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blog.resomail.com/?p=18</guid>
		<description><![CDATA[So the testing has started, we have a limited resource test configuration put in open without promoting it (just to a limited set of people), so we&#8217;ll be able fix bugs faster than those bugs are found. Also I&#8217;ve decided to change sale pitch on front page: ResoMail.com to match close the audience of alpha [...]]]></description>
			<content:encoded><![CDATA[<p>So the testing has started, we have a limited resource test configuration put in open without promoting it (just to a limited set of people), so we&#8217;ll be able fix bugs faster than those bugs are found. Also I&#8217;ve decided to change sale pitch on front page: <a title="ResoMail secure private mail" href="http://resomail.com">ResoMail.com</a> to match close the audience of alpha testers, which I feel will consist of tech savvy guys who know what encryption is.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.resomail.com/2009/06/testing-started/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ResoMail deployment</title>
		<link>http://blog.resomail.com/2009/06/resomail-deployment/</link>
		<comments>http://blog.resomail.com/2009/06/resomail-deployment/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 14:46:29 +0000</pubDate>
		<dc:creator>sergio</dc:creator>
				<category><![CDATA[ResoMail]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[deployment]]></category>
		<category><![CDATA[new product]]></category>

		<guid isPermaLink="false">http://blog.resomail.com/?p=13</guid>
		<description><![CDATA[So now we have all the functionality we&#8217;ve planed for an alpha test of ResoMail. During the alph test we&#8217;ll be offering free mail accounts and free domain addresses under .free root domain name. For mail accounts there will be an automated registration tool &#8211; a web application which will be deployed as a standard [...]]]></description>
			<content:encoded><![CDATA[<p>So now we have all the functionality we&#8217;ve planed for an alpha test of <a title="ResoMail secure cryptographic mail" href="http://resomail.com">ResoMail</a>. During the alph test we&#8217;ll be offering free mail accounts and free domain addresses under .free root domain name. For mail accounts there will be an automated registration tool &#8211; a web application which will be deployed as a standard servlet container and will register mail accounts under secure domains *@mail.free or *@email.free . We&#8217;ll have to deploy a resomail server for free mail and dns functionality on separate server. Domain names will be generated on request, probable we&#8217;ll open in the <a title="ResoMail forum" href="http://resomail.com/forum/">forum</a> a topic for it. We plan to implement automated domain name registration in the later releases.</p>
<p>So we plan to be ready in less than a week, we&#8217;ll make an announcement here when we&#8217;ll be ready.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.resomail.com/2009/06/resomail-deployment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What is ResoMail?</title>
		<link>http://blog.resomail.com/2009/05/what-is-resomail/</link>
		<comments>http://blog.resomail.com/2009/05/what-is-resomail/#comments</comments>
		<pubDate>Wed, 06 May 2009 01:29:45 +0000</pubDate>
		<dc:creator>sergio</dc:creator>
				<category><![CDATA[ResoMail]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[scurity]]></category>

		<guid isPermaLink="false">http://blog.resomail.com/?p=6</guid>
		<description><![CDATA[ResoMail is a secure electronic mail system, which is based on public key infrastructure, and offers in contrast to current postcard e-mail a real secure and private mail. It&#8217;s a separate system which have independent DNS, secure domains (equivalent with current domains with SSL) and secure mail.
]]></description>
			<content:encoded><![CDATA[<p><a title="ResoMail secure mail" href="http://resomail.com">ResoMail</a> is a secure electronic mail system, which is based on public key infrastructure, and offers in contrast to current postcard e-mail a real secure and private mail. It&#8217;s a separate system which have independent DNS, secure domains (equivalent with current domains with SSL) and secure mail.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.resomail.com/2009/05/what-is-resomail/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
