<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for dominykas.com</title>
	<atom:link href="http://www.dominykas.com/comments.rss2.xml" rel="self" type="application/rss+xml" />
	<link>http://www.dominykas.com</link>
	<description>I&#039;d like to someday write a book about asking the right questions</description>
	<lastBuildDate>Tue, 09 Aug 2011 01:58:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on (Solved) troubles with Ubuntu, VirtualBox, OpenVZ/Proxmox and MySQL by Abdoulaye Siby</title>
		<link>http://www.dominykas.com/2010/05/solved-troubles-with-ubuntu-virtualbox-openvzproxmox-and-mysql.html/comment-page-1#comment-7756</link>
		<dc:creator>Abdoulaye Siby</dc:creator>
		<pubDate>Tue, 09 Aug 2011 01:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dominykas.com/?p=108#comment-7756</guid>
		<description>Interesting. I thought I was the first one to have this idea. To good this is that at least I know now that what I was doing is not that crazy at all. I also have Windows 7 and Proxmox running on VirtualBox. It works flawlessly and take far less resources when using ONLY OpenVZ containers.

I have an annoyance that I am experiencing though ... My home network is using 192.168.2.x ... and Proxmox is using 192.168.2.15 (static IP configured inside Proxmox)

Unfortunately, as soon as I am on another network, the IP 192.168.2.15 will be unavailable. Maybe it&#039;s just a matter of create an alias for the interface and use that IP instead of the one that matches the current network.

Cheers.</description>
		<content:encoded><![CDATA[<p>Interesting. I thought I was the first one to have this idea. To good this is that at least I know now that what I was doing is not that crazy at all. I also have Windows 7 and Proxmox running on VirtualBox. It works flawlessly and take far less resources when using ONLY OpenVZ containers.</p>
<p>I have an annoyance that I am experiencing though &#8230; My home network is using 192.168.2.x &#8230; and Proxmox is using 192.168.2.15 (static IP configured inside Proxmox)</p>
<p>Unfortunately, as soon as I am on another network, the IP 192.168.2.15 will be unavailable. Maybe it&#8217;s just a matter of create an alias for the interface and use that IP instead of the one that matches the current network.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on javascript:void(0) must die by stephband</title>
		<link>http://www.dominykas.com/2009/12/javascript-void-must-die.html/comment-page-1#comment-1354</link>
		<dc:creator>stephband</dc:creator>
		<pubDate>Sat, 09 Oct 2010 18:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.dominykas.com/?p=8#comment-1354</guid>
		<description>Right on. We use a tags with href=&quot;#action_name&quot; at webdoc.com - and that&#039;s because I have been bitten by button style before. I haven&#039;t tested them in a year, but back when I did FireFox was the culprit - it was impossible to remove overflow: hidden, among other things, I seem to remember.

Anyway, at some point I&#039;m going to move our buttons to being command tags, the new html5 element for application commands.  In the spec, it appears you can replace li tags in a ul or menu with command tags, which is pretty groovy.</description>
		<content:encoded><![CDATA[<p>Right on. We use a tags with href=&#8221;#action_name&#8221; at webdoc.com &#8211; and that&#8217;s because I have been bitten by button style before. I haven&#8217;t tested them in a year, but back when I did FireFox was the culprit &#8211; it was impossible to remove overflow: hidden, among other things, I seem to remember.</p>
<p>Anyway, at some point I&#8217;m going to move our buttons to being command tags, the new html5 element for application commands.  In the spec, it appears you can replace li tags in a ul or menu with command tags, which is pretty groovy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on (Solved) troubles with Ubuntu, VirtualBox, OpenVZ/Proxmox and MySQL by David Sugar</title>
		<link>http://www.dominykas.com/2010/05/solved-troubles-with-ubuntu-virtualbox-openvzproxmox-and-mysql.html/comment-page-1#comment-1069</link>
		<dc:creator>David Sugar</dc:creator>
		<pubDate>Mon, 13 Sep 2010 21:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dominykas.com/?p=108#comment-1069</guid>
		<description>The strange thing is your weird setup actually makes perfect sense to me, at least for setting up testing appliances.  I was thinking of doing a sipwitch testing appliance and a backup/test site for my main public site, which uses mediawiki, and maybe something for something else.  None of these really require a full vm by themselves (which seems a huge waste of resources), I did not wish to mix them together in testing, nor did I wish to dedicate a box just for things that have rather transient use.  Disk space and memory I do have plenty of on my main dev box, I too have become rather familiar with virtualbox, and I also like it&#039;s small footprint and simplicity.

It&#039;s possible with the newer kernel in proxmox 1.6 (it now uses 2.6.32) will remap /dev/sda correctly from first boot, though I think I may try the virtualbox sata if it has better performance.</description>
		<content:encoded><![CDATA[<p>The strange thing is your weird setup actually makes perfect sense to me, at least for setting up testing appliances.  I was thinking of doing a sipwitch testing appliance and a backup/test site for my main public site, which uses mediawiki, and maybe something for something else.  None of these really require a full vm by themselves (which seems a huge waste of resources), I did not wish to mix them together in testing, nor did I wish to dedicate a box just for things that have rather transient use.  Disk space and memory I do have plenty of on my main dev box, I too have become rather familiar with virtualbox, and I also like it&#8217;s small footprint and simplicity.</p>
<p>It&#8217;s possible with the newer kernel in proxmox 1.6 (it now uses 2.6.32) will remap /dev/sda correctly from first boot, though I think I may try the virtualbox sata if it has better performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on javascript:void(0) must die by Dominykas</title>
		<link>http://www.dominykas.com/2009/12/javascript-void-must-die.html/comment-page-1#comment-6</link>
		<dc:creator>Dominykas</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.dominykas.com/?p=8#comment-6</guid>
		<description>Mark, even if you hadn&#039;t provided real URLs from the start, you can always link to named anchors, i.e. #something - as long as #something exists (even a div with an id will do) - it&#039;s better than void. Forgot to include that in the post :)

I did, indeed, not elaborate on the whole GET/POST topic - but hey - it&#039;s for future use :) Especially if I get a chance to publish the security slides.

As for redirecting to a new form - the same URL can handle both AJAX, and non-AJAX (/myResource?delete=yes&amp;confirmed=yes). Assuming you&#039;re already doing a POST, you just need to check for AJAX header and return appropriate view - be it MVC or not - if (AJAX) { echo JSON() } else { echo HTML() } - not that much code required!

The only real thing to build is the &quot;interstitial form&quot; - but that can easily be frameworkified. In reality, supporting this is not even 10% overhead on individual feature, compared to the hoops that you have to implement for it to work (access checking, validation, escaping, connections, etc etc). And it&#039;s even more negligible in the big picture of the overall project (whatever the case may be) - you need frameworks developed, etc etc.

There&#039;s no reason to be lazy, whether client pays for it or not. If one starts doing that now, and charging their customers 5% more, without even negotiating the &quot;accessibility&quot; aspect - the &quot;just do it&quot; way - it&#039;s still just just more than inflation in Ireland in 2008. And you get the bragging rights as well, even if the customer doesn&#039;t realize that :)</description>
		<content:encoded><![CDATA[<p>Mark, even if you hadn&#8217;t provided real URLs from the start, you can always link to named anchors, i.e. #something &#8211; as long as #something exists (even a div with an id will do) &#8211; it&#8217;s better than void. Forgot to include that in the post :)</p>
<p>I did, indeed, not elaborate on the whole GET/POST topic &#8211; but hey &#8211; it&#8217;s for future use :) Especially if I get a chance to publish the security slides.</p>
<p>As for redirecting to a new form &#8211; the same URL can handle both AJAX, and non-AJAX (/myResource?delete=yes&#038;confirmed=yes). Assuming you&#8217;re already doing a POST, you just need to check for AJAX header and return appropriate view &#8211; be it MVC or not &#8211; if (AJAX) { echo JSON() } else { echo HTML() } &#8211; not that much code required!</p>
<p>The only real thing to build is the &#8220;interstitial form&#8221; &#8211; but that can easily be frameworkified. In reality, supporting this is not even 10% overhead on individual feature, compared to the hoops that you have to implement for it to work (access checking, validation, escaping, connections, etc etc). And it&#8217;s even more negligible in the big picture of the overall project (whatever the case may be) &#8211; you need frameworks developed, etc etc.</p>
<p>There&#8217;s no reason to be lazy, whether client pays for it or not. If one starts doing that now, and charging their customers 5% more, without even negotiating the &#8220;accessibility&#8221; aspect &#8211; the &#8220;just do it&#8221; way &#8211; it&#8217;s still just just more than inflation in Ireland in 2008. And you get the bragging rights as well, even if the customer doesn&#8217;t realize that :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on javascript:void(0) must die by Mark Lennox</title>
		<link>http://www.dominykas.com/2009/12/javascript-void-must-die.html/comment-page-1#comment-5</link>
		<dc:creator>Mark Lennox</dc:creator>
		<pubDate>Thu, 03 Dec 2009 13:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.dominykas.com/?p=8#comment-5</guid>
		<description>Using real URL&#039;s is great as long as you have built that into your design from the start. You should probably mention that using GET&#039;s to update/delete is probably not a good thing - which people might implement while taking a short-cut.

Redirecting to a new form from the link to support regressive dehancement ;) is my favourite choice, also links are crawlable, URL&#039;s don&#039;t need to be maintained in server-side AND javascript etc. - but it means more coding, and the client won&#039;t pay for that (time, not necessarily money). But that opens up the whole question of selling basic functionality to the business, which is always a hard sell - &quot;gimme what I want, not what I need&quot;</description>
		<content:encoded><![CDATA[<p>Using real URL&#8217;s is great as long as you have built that into your design from the start. You should probably mention that using GET&#8217;s to update/delete is probably not a good thing &#8211; which people might implement while taking a short-cut.</p>
<p>Redirecting to a new form from the link to support regressive dehancement ;) is my favourite choice, also links are crawlable, URL&#8217;s don&#8217;t need to be maintained in server-side AND javascript etc. &#8211; but it means more coding, and the client won&#8217;t pay for that (time, not necessarily money). But that opens up the whole question of selling basic functionality to the business, which is always a hard sell &#8211; &#8220;gimme what I want, not what I need&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

