Re: [Jpwsafe-devel] S3 storage issues

[Michael T. <mic...@gm...>]

David,

On Mon, Feb 16, 2009 at 4:23 PM, David <ro...@us...> wrote:

> Hi Mike (and all),
>
> congrats for your breakthrough! I'm eager to try your lib on my mobile -
> would you like to have a new sub project for the J2Me lib etc. ?
> Probably it makes sense to make it a Netbeans based project, with
> Netbeans being the best platform for J2ME.


It is actually pretty complicated.  I can develop in NetBeans and it works
nicely.  BUT, I cannot build a Blackberry jar in NetBeans (I can build the
jar, but the Blackberry won't accept it).  Even more complicated, I want to
keep the library separate from the UI for various reasons AND I have trimmed
Bouncy Castle down to only the bits I need and I keep that separate too.
The result is a fairly complicated system that involves a couple of
different parts of the repository being assembled together via some
svn:externals.

At the moment I'm hosting everything myself and trying to keep it separate
simply to avoid any license/copyright issues (everything I did for J2ME was
from scratch).  Plus, I like using Trac and so I'm taking full advantage of
having that available to me.  :-)  So for now I don't really want to mix
things.  I have a couple of other J2ME security related applications in
development and I think it makes more sense to cluster those together.


> Fair enough for the reader, it's good to have a working product, even if
> it only has a part of the complete feature set. In fact, Passwordsafe
> SWT is in a constant partly working state compared to the native PC
> version!


Writing back (and local caching for when you are off the network) are on the
plan and should not be too hard to do.  But read-only is my first step.  It
has the added benefit of being useful too.


> Well put. Sorry, it's German netiquette jargon, meaning text on top,
> full quote on the bottom. It's part of my personal preference to "don't
> repeat yourself", that I try to adhere to in code as well. So, I prefer
> inline quoting as I'm doing here. Please simply take it as a possible
> way of improving mailing effectiveness.


AHH!  Yes, we call this "top posting".  I can certainly do the inline
response.


> Cheers,
> David
>

--
Mike