<?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: Midlet Signing</title>
	<link>http://blog.javia.org/midlet-signing/</link>
	<description>Mihai Preda on mobile applications</description>
	<pubDate>Tue, 06 Jan 2009 09:32:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: Bestyagna</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12669</link>
		<dc:creator>Bestyagna</dc:creator>
		<pubDate>Wed, 24 Sep 2008 04:17:08 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12669</guid>
		<description>Nice blog, very informative. Just to let everyone know that beside all this frustration thawte has increase there code signing certificate to $299.</description>
		<content:encoded><![CDATA[<p>Nice blog, very informative. Just to let everyone know that beside all this frustration thawte has increase there code signing certificate to $299.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: atleta</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12655</link>
		<dc:creator>atleta</dc:creator>
		<pubDate>Mon, 28 Jul 2008 10:45:31 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12655</guid>
		<description>Interestign article. At least answered the hard question 'which cert to buy'. I was afraid to find what you were saying because of the fact that I couldn't google up a page that would say something concrete.

However Sean Sealey's comment is also very valuable. It seems that the misconception that the midlets _have to_ be javaverified for each device is quite widespead. I believed it for the first sight too. The reality is better fortunately. Not if paying 240 EUR, that is $360 for one version would be such a great option. It's only viable for 'write and forget' types of applications, like games, etc.</description>
		<content:encoded><![CDATA[<p>Interestign article. At least answered the hard question &#8216;which cert to buy&#8217;. I was afraid to find what you were saying because of the fact that I couldn&#8217;t google up a page that would say something concrete.</p>
<p>However Sean Sealey&#8217;s comment is also very valuable. It seems that the misconception that the midlets _have to_ be javaverified for each device is quite widespead. I believed it for the first sight too. The reality is better fortunately. Not if paying 240 EUR, that is $360 for one version would be such a great option. It&#8217;s only viable for &#8216;write and forget&#8217; types of applications, like games, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12648</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 09 Jul 2008 12:41:58 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12648</guid>
		<description>vmlog: If you are accessing the filesystem to load resources (i.e. to get around the midlet size limitations) then I've found a way to store all your resources in one file so you only need to give permission once.

Basically, there is no seek function so you can't go seek randomly in the file. You can however close the InputStream and open a new one. This gets you back to the beginning of the file. You have to keep the FileConnection open otherwise it asks for your permission to read the file again.

I'll post the code somewhere if people are interested...</description>
		<content:encoded><![CDATA[<p>vmlog: If you are accessing the filesystem to load resources (i.e. to get around the midlet size limitations) then I&#8217;ve found a way to store all your resources in one file so you only need to give permission once.</p>
<p>Basically, there is no seek function so you can&#8217;t go seek randomly in the file. You can however close the InputStream and open a new one. This gets you back to the beginning of the file. You have to keep the FileConnection open otherwise it asks for your permission to read the file again.</p>
<p>I&#8217;ll post the code somewhere if people are interested&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Eriksson</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12643</link>
		<dc:creator>Henrik Eriksson</dc:creator>
		<pubDate>Sat, 05 Jul 2008 00:06:16 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12643</guid>
		<description>Have a look at android: http://code.google.com/android and forget about signing midlets!</description>
		<content:encoded><![CDATA[<p>Have a look at android: <a href="http://code.google.com/android" rel="nofollow">http://code.google.com/android</a> and forget about signing midlets!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yar</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12642</link>
		<dc:creator>Yar</dc:creator>
		<pubDate>Sat, 14 Jun 2008 07:58:36 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12642</guid>
		<description>Yes, it is stupid and painful, BUT I believe that still we have a great development environment - J2ME, with big potential.
1. From your experience, how do users react to the questions 'Do you allow... etc.' ?
2. You can make it less confusing for an end user, if first, at the very beginning of an operation like file access, you let them know - with an Alert - that they should press Yes if their phone asks them for permission. That's what I do in my application.
3. Make as many options for an user as possible. i.e they can access their phone file system with FileConnection JSR-75, but whey should be able to do it another way like access some file manually, etc.</description>
		<content:encoded><![CDATA[<p>Yes, it is stupid and painful, BUT I believe that still we have a great development environment - J2ME, with big potential.<br />
1. From your experience, how do users react to the questions &#8216;Do you allow&#8230; etc.&#8217; ?<br />
2. You can make it less confusing for an end user, if first, at the very beginning of an operation like file access, you let them know - with an Alert - that they should press Yes if their phone asks them for permission. That&#8217;s what I do in my application.<br />
3. Make as many options for an user as possible. i.e they can access their phone file system with FileConnection JSR-75, but whey should be able to do it another way like access some file manually, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Muhammad Aamir</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12636</link>
		<dc:creator>Muhammad Aamir</dc:creator>
		<pubDate>Wed, 21 May 2008 10:39:08 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12636</guid>
		<description>Interesting article.</description>
		<content:encoded><![CDATA[<p>Interesting article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sven L.</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12617</link>
		<dc:creator>Sven L.</dc:creator>
		<pubDate>Sat, 26 Apr 2008 15:16:59 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12617</guid>
		<description>Hello Mihai Preda,

Thank you for this absolutely great summery of the signing problematic. We spend a lot of time to understand the difference between normal code signing certificates and the Java verified program. Your blog describes the difference in an excellent way.

Best regards

Sven Luzar</description>
		<content:encoded><![CDATA[<p>Hello Mihai Preda,</p>
<p>Thank you for this absolutely great summery of the signing problematic. We spend a lot of time to understand the difference between normal code signing certificates and the Java verified program. Your blog describes the difference in an excellent way.</p>
<p>Best regards</p>
<p>Sven Luzar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angery developer</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12615</link>
		<dc:creator>Angery developer</dc:creator>
		<pubDate>Thu, 24 Apr 2008 04:00:51 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12615</guid>
		<description>This is a great article. I have just spent the last 2 days trying to find out how to get a certificate for a small personal java application and have come to the conclusion that I must first fork up at least 150$. Not only that- that is just for TESTING! What if I fail?! I can't even test on a real phone, only emulators! 

That is absurd. I was planning on accessing my own PIM, and that was it. Nothing commercial, yet I can't even do that. Honestly, this is quite outrageous. What the community needs to do is have a website where developers can submit their projects, then a selected team of advanced programmers looks over it. I can guaruntee that the developers in the community are just as good at testing as the "professionals", and I'm sure they wouldn't mind doing their own testing. Anyway, if anyone is starting an initiative to create an "open-source" certification system, let me know.</description>
		<content:encoded><![CDATA[<p>This is a great article. I have just spent the last 2 days trying to find out how to get a certificate for a small personal java application and have come to the conclusion that I must first fork up at least 150$. Not only that- that is just for TESTING! What if I fail?! I can&#8217;t even test on a real phone, only emulators! </p>
<p>That is absurd. I was planning on accessing my own PIM, and that was it. Nothing commercial, yet I can&#8217;t even do that. Honestly, this is quite outrageous. What the community needs to do is have a website where developers can submit their projects, then a selected team of advanced programmers looks over it. I can guaruntee that the developers in the community are just as good at testing as the &#8220;professionals&#8221;, and I&#8217;m sure they wouldn&#8217;t mind doing their own testing. Anyway, if anyone is starting an initiative to create an &#8220;open-source&#8221; certification system, let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vmlog</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12597</link>
		<dc:creator>vmlog</dc:creator>
		<pubDate>Mon, 25 Feb 2008 03:43:27 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12597</guid>
		<description>Thanks for the very good article.. Wish some manufacturer comes across this article...

Do we still have the issues? I am trying to develop a midlet for my nokia 6300. As I couldn't sign it, the phone asks permission each time my midlet tries to access file system.</description>
		<content:encoded><![CDATA[<p>Thanks for the very good article.. Wish some manufacturer comes across this article&#8230;</p>
<p>Do we still have the issues? I am trying to develop a midlet for my nokia 6300. As I couldn&#8217;t sign it, the phone asks permission each time my midlet tries to access file system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vmlog</title>
		<link>http://blog.javia.org/midlet-signing/#comment-12596</link>
		<dc:creator>vmlog</dc:creator>
		<pubDate>Mon, 25 Feb 2008 03:41:28 +0000</pubDate>
		<guid>http://blog.javia.org/midlet-signing/#comment-12596</guid>
		<description>Very good article.. Wish some manufacturer comes across this article...

Do we still have the issues? I am trying to develop a midlet for my nokia 6300. As I couldn't sign it, the phone asks permission each time my midlet tries to access file system.</description>
		<content:encoded><![CDATA[<p>Very good article.. Wish some manufacturer comes across this article&#8230;</p>
<p>Do we still have the issues? I am trying to develop a midlet for my nokia 6300. As I couldn&#8217;t sign it, the phone asks permission each time my midlet tries to access file system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
