First let me say that it is great news! Android seems to provide a relative lightweight but powerful API.
Google seems to understand that a core API should provide the building blocks (e.g. OpenGL binding) and lets the developers create the optional higher level components themselves. Androids could be a response to the current J2SE bloating and replace the J2SE platform altogether!
Furthermore, Androids is not J2ME based but J2SE based with class parameterization support!
This is very exciting as the philosophy of Android is about the same as the Javolution library (which could complement it nicely): Fast, Responsive & Seamless:)
The real-time parser looks and behaves like a SAX2 parser. The only difference is that Strings have been replaced by CharSequence.
In other words, they will be some twinking in your code but not much.
You can also use the SAX2 wrapper (XmlReaderImpl) in which case you don't have to change anything (but not as fast as String are dynamically allocated during processing).
Slashdot Mirror
First let me say that it is great news! Android seems to provide a relative lightweight but powerful API. Google seems to understand that a core API should provide the building blocks (e.g. OpenGL binding) and lets the developers create the optional higher level components themselves. Androids could be a response to the current J2SE bloating and replace the J2SE platform altogether! Furthermore, Androids is not J2ME based but J2SE based with class parameterization support! This is very exciting as the philosophy of Android is about the same as the Javolution library (which could complement it nicely): Fast, Responsive & Seamless :)
The real-time parser looks and behaves like a SAX2 parser. The only difference is that Strings have been replaced by CharSequence. In other words, they will be some twinking in your code but not much. You can also use the SAX2 wrapper (XmlReaderImpl) in which case you don't have to change anything (but not as fast as String are dynamically allocated during processing).