BTW, I just built the protobuf-java-2.2.0.jar file and noticed it is just over 300K in size. Anyone else using protocol buffers from an android device? Does it necessarily need to be so big, or am I missing some build param? It just doubled my application size.
-broc On Sep 24, 7:09 am, "nEx.Software" <[email protected]> wrote: > You could tryprotocolbuffers...http://code.google.com/apis/protocolbuffers/ > > On Sep 23, 1:11 pm, Evan Ruff <[email protected]> wrote: > > > > > You know, > > > I would be awesome if we could get some sort of native C++ system > > service to solve this issue. I don't really care WHAT the > > implementation is, so long as it's blazing fast. > > > Is that even part of the Android thing? > > > E > > > On Sep 23, 4:07 pm, WoodManEXP <[email protected]> wrote: > > > > Evan, As far as I can tell there is little support native to Android > > > for what you are lookng for. It has good basic http communication > > > support but not much higher level abstractions. That being said you > > > could write a layer to do the serialization into a stream and then > > > HTTP it to the server to be deserialized. On the server it would > > > reconstruct from a stream you get out of an HTTP POST payload. Its not > > > fancy but it would definitly work. I simply POST simple XML to the > > > server and DOM parse it out rather then trying to send objects. > > > > I imagine Google's concern is two-fold a) resource constraints for the > > > development team to add such support and b) Its alot of s'ware to add > > > to the system at this time. > > > > Sorry to not be of more help. > > > > On Sep 23, 3:40 pm, Evan Ruff <[email protected]> wrote: > > > > > I have a Tomcat Server in front of a Servlet that gets/stores > > > > information in a MySQL Database. My Android application needs to get/ > > > > put information on to this server. I control both ends of the > > > > communication, so I've basically been exploring the "best" way to send > > > > information back and forth. So far, I've tried Jackson for JSON and > > > > the native Java Serialization packages. My object is relatively > > > > complex and completely serializable. I have no desire to write a > > > > "custom" guy at all, as I doubt I'd actually be able to improve on > > > > most of the packages. > > > > > Times are from when the response lands on the Android device until the > > > > Object is fully cast: > > > > > Jackson for JSON 1.0: 17.176 seconds. > > > > Native Java Serialization: 36.132 seconds. > > > > > WOW. Java Serialization is a D-O-G. > > > > > So with that being said, are there any other strategies/packages I > > > > should try to get information to/from my server? > > > > > Thanks! > > > > > Evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
