<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: JAD is BAD</title>
	<link>http://blog.javia.org/jad-is-bad/</link>
	<description>Mihai Preda on mobile applications</description>
	<pubDate>Tue, 06 Jan 2009 07:56:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: nicole</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-12495</link>
		<dc:creator>nicole</dc:creator>
		<pubDate>Wed, 19 Sep 2007 13:24:19 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-12495</guid>
		<description>The idea of the JAD first to ensure it meets requirements is not a bad idea, and as applications get bigger and bigger it will continue making sense, especially as JAD files will provide information such as library, and library dependencies and its good</description>
		<content:encoded><![CDATA[<p>The idea of the JAD first to ensure it meets requirements is not a bad idea, and as applications get bigger and bigger it will continue making sense, especially as JAD files will provide information such as library, and library dependencies and its good</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicole</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-12494</link>
		<dc:creator>nicole</dc:creator>
		<pubDate>Wed, 19 Sep 2007 13:22:58 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-12494</guid>
		<description>From experience when pushing Midlets via Bluetooth the JAD/JAR files does become a problem, in the end you tend to just push the JAR file only. But in general I agree with Ortiz comments with respect to OTA via carrier.</description>
		<content:encoded><![CDATA[<p>From experience when pushing Midlets via Bluetooth the JAD/JAR files does become a problem, in the end you tend to just push the JAR file only. But in general I agree with Ortiz comments with respect to OTA via carrier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicole</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-12493</link>
		<dc:creator>nicole</dc:creator>
		<pubDate>Wed, 19 Sep 2007 13:21:42 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-12493</guid>
		<description>its,a good thing to download something from JAD cause it can help any one with anything that you download from,so i prefer this one in stared of something else.</description>
		<content:encoded><![CDATA[<p>its,a good thing to download something from JAD cause it can help any one with anything that you download from,so i prefer this one in stared of something else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Lam</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-1491</link>
		<dc:creator>Jason Lam</dc:creator>
		<pubDate>Mon, 19 Feb 2007 03:09:53 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-1491</guid>
		<description>From experience when pushing Midlets via Bluetooth the JAD/JAR files does become a problem, in the end you tend to just push the JAR file only.  But in general I agree with Ortiz comments with respect to OTA via carrier.</description>
		<content:encoded><![CDATA[<p>From experience when pushing Midlets via Bluetooth the JAD/JAR files does become a problem, in the end you tend to just push the JAR file only.  But in general I agree with Ortiz comments with respect to OTA via carrier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders Borg</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-737</link>
		<dc:creator>Anders Borg</dc:creator>
		<pubDate>Mon, 29 Jan 2007 21:38:45 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-737</guid>
		<description>There's a good reason for using a JAD, but this approach is yet not used much: Let's say you've made an application that wants to check regularly if there's a new version of it. It could then download and parse the JAD and compare the MIDlet-Version in there with that of the currently installed MIDlet. If there's a newer version, the user could be asked to upgrade.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a good reason for using a JAD, but this approach is yet not used much: Let&#8217;s say you&#8217;ve made an application that wants to check regularly if there&#8217;s a new version of it. It could then download and parse the JAD and compare the MIDlet-Version in there with that of the currently installed MIDlet. If there&#8217;s a newer version, the user could be asked to upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wap Review</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-485</link>
		<dc:creator>Wap Review</dc:creator>
		<pubDate>Sun, 07 Jan 2007 22:15:14 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-485</guid>
		<description>&lt;strong&gt;Carnival Time!...&lt;/strong&gt;


Photo by Rick Takagi 	Some rights reserved.
After a long holiday break, the Carnival of the Mobilists is back. I'm honored to host it here at Wap Review with a great selection of posts from all areas of the mobile scene.
History and Prognostication: ...</description>
		<content:encoded><![CDATA[<p><strong>Carnival Time!&#8230;</strong></p>
<p>Photo by Rick Takagi 	Some rights reserved.<br />
After a long holiday break, the Carnival of the Mobilists is back. I&#8217;m honored to host it here at Wap Review with a great selection of posts from all areas of the mobile scene.<br />
History and Prognostication: &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. Enrique Ortiz</title>
		<link>http://blog.javia.org/jad-is-bad/#comment-281</link>
		<dc:creator>C. Enrique Ortiz</dc:creator>
		<pubDate>Tue, 12 Dec 2006 21:25:42 +0000</pubDate>
		<guid>http://blog.javia.org/jad-is-bad/#comment-281</guid>
		<description>I've to disagree on this one :-).  The whole archiver approach to extract the manifest is just more work than including the JAD file in the first place. The idea of the JAD first to ensure it meets requirements is not a bad idea, and as applications get bigger and bigger it will continue making sense, especially as JAD files will provide information such as library, and library dependencies and versions, -- no need to download a large JAR (particularly if there is no flat-rate) if anyways it won't meet pre-requisistes.

ceo</description>
		<content:encoded><![CDATA[<p>I&#8217;ve to disagree on this one :-).  The whole archiver approach to extract the manifest is just more work than including the JAD file in the first place. The idea of the JAD first to ensure it meets requirements is not a bad idea, and as applications get bigger and bigger it will continue making sense, especially as JAD files will provide information such as library, and library dependencies and versions, &#8212; no need to download a large JAR (particularly if there is no flat-rate) if anyways it won&#8217;t meet pre-requisistes.</p>
<p>ceo</p>
]]></content:encoded>
	</item>
</channel>
</rss>
