-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, after a bit of study, I've started working with Android and I've a first prototype ported from my mobile stuff.
Now, a question. At the moment I don't need a database for it, because the application is very simple and the data that it needs to manipulate are simple (and small) enough to be serializable. Another bunch of read only data is stored in JSON and at the moment I'm fine with reading it at boot and keeping in memory. But, of course, having a real database in future would be a plus. If I could choose, I'd like to use OpenSesame (an RDF triple store) since it's what I'm using for the same data in other contexts (desktop and server). Still, I fear it could not work with Android or be too heavy. All the objects of my APIs are properly separated in API and SPI, so I can provide other implementations, if I need. I suppose Derby works fine with Android - but are there other choices? Thanks. - -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people fabrizio.giud...@tidalwave.it -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvLk9cACgkQeDweFqgUGxfjrQCgke6Csv2mIlgD4qjO16Yn+CyR HT8An3f47KScQbftUQa3kOdZTB3QKSxF =Bx77 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
