Mined Opinions For API: com.google.protobuf

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • Or [Protocol Buffers]( URL_http://code.google.com/p/protobuf /) since it's supported by almost any language, results in smaller serialized data and you don't even have to write a single line of code to parse / serialize it.. details
  • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method.. details
  • The protobuf objects have serialization methods to bytes, it's very efficient and compresses really well.. details
  • thanks for the answer.. details
  • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most).. details
  • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader.. details
  • Other things you can do is call class in each and get the classloader and fool around with getting the classloaders parents as well to see what the classloader heirarchy looks like.. details
  • As a temporary solution this works, but I would like to know the correct way to deal with this problem.. details
  • Interestingly the class it says it can't find is different: CODESNIPPET_JAVA6 .. details
  • I am working with protobufs with the play framework 2.1.3 without issues.. details
  • I also use it as the serialization for my RPC-style APIs for fairly high traffic systems, although I prefer using Protobuf for those when possible.. details
  • One last note : The object mapper is thread safe and having one static instance like in the example I just submitted will prevent you from having the slight instantiation overhead.. details
  • JAX-RS implementations support the type out of the box and it sounds like an easy solution to leave the rest to the browser.. details
  • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON.. details
  • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON.. details
  • EDIT added information asked by the comments -- thanks!. details
  • readable code/architecture In short, which of the 3 formats mentioned above fits those requirements the best, given that I'm using a Java REST service on the backend?. details
  • (If the fact that I'm using a Java REST service -- instead of say, a servlet -- to upload the files is going to be the biggest slowdown, that's also a good answer!). details
  • It's a JavaScript frontend, so json would be preferred.. details
  • performant and efficient data transfer.. details
  • In order to get the data from the backend to the frontend you have to use some data interchange format like CODETERM3 or CODETERM4 .. details
  • The biggest advantage of applying this service oriented approach** to your own project is that you decouple your components (frontend and backend).. details
  • The advantage of CODETERM5 is, that is fairly efficient compared to CODETERM6 and well accepted.. details
  • The advantage of CODETERM5 is, that is fairly efficient compared to CODETERM6 and well accepted.. details
  • These are very useful when you want to include the services in your applications.. details
  • If you are not particularly tied to JSON, URL_http://code.google.com/p/protobuf/ [Protocol-Buffers] is worth checking out.. details
  • URL_http://jabsorb.org/ [Jabsorb] also has good (de)serialization package.. details
  • It also helps to have "standard" persistence framework.. details
  • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like URL_http://code.google.com/apis/protocolbuffers/docs/overview.html [google-protocol-buffers] Also check out the URL_http://java.sun.com/j2se/1.3/docs/api/java/io/Externalizable.html [Externalizable] interface for custom serialisation .. details
  • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like URL_http://code.google.com/apis/protocolbuffers/docs/overview.html [google-protocol-buffers] Also check out the URL_http://java.sun.com/j2se/1.3/docs/api/java/io/Externalizable.html [Externalizable] interface for custom serialisation .. details
  • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.. details
  • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.. details
  • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).. details
  • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).. details
  • Check out URL_https://code.google.com/p/jbox2d/source/browse/trunk/jbox2d- serialization/src/main/java/org/jbox2d/serialization/pb/PbSerializer.java [PbSerializer] and here is documentation on protobufs: URL_https://code.google.com/p/protobuf/ [ URL_https://code.google.com/p/protobuf/ ] .. details
  • Another very useful method to play around with when debugging is XXXXX.class.getProtectionDomain().getCodeSource().getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf-java-format is having a problem loading and also any class from protobuf-java-format.. details
  • If play is started in production mode I do not have any errors.. details
  • I can run without problems: CODESNIPPET_JAVA4 .. details
  • This leads to the following error when running in dev mode (started with play run) CODESNIPPET_JAVA3 .. details
  • Trying to covert any protobuf to JSON using CODESNIPPET_JAVA2 .. details
  • I have been able to get it to work in dev mode if I put the source code for protobuf-java-format in my app folder.. details
  • NoClassDefFoundError is thrown when I try to use any static method from protobuf-java-format library.. details
  • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path.. details
  • By doing this you achieve following things: Make your services available to other (web-)applications and users because your service exposes a specific API/data exchange format that they can use.. details
  • Over the years I have tried quite a few options or serialization/deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here :-) Right now we are using JSON encoding almost exclusively for both Java-to-Java and JS-to-Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient).. details
Summaries the opinions about com.google.protobuf using topic modeling.
  • 0. serialisation buffers hood low custom throughput externalizable performant transfer frontend: 3
    • performant and efficient data transfer.. details
    • If you are not particularly tied to JSON, Protocol-Buffers is worth checking out.. details
    • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like google-protocol-buffers Also check out the Externalizable interface for custom serialisation .. details
  • 1. classloader thing protobufs answer rest service fact classloaders heirarchy upload: 7
    • thanks for the answer.. details
    • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most).. details
    • Other things you can do is call class in each and get the classloader and fool around with getting the classloaders parents as well to see what the classloader heirarchy looks like.. details
    • I am working with protobufs with the play framework 2.1.3 without issues.. details
    • (If the fact that I'm using a Java REST service -- instead of say, a servlet -- to upload the files is going to be the biggest slowdown, that's also a good answer!). details
    • readable code/architecture In short, which of the 3 formats mentioned above fits those requirements the best, given that I'm using a Java REST service on the backend?. details
    • These are very useful when you want to include the services in your applications.. details
  • 2. backend service frontend performant call big browser approach serialize pass: 5
    • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method.. details
    • As a temporary solution this works, but I would like to know the correct way to deal with this problem.. details
    • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON.. details
    • The biggest advantage of applying this service oriented approach** to your own project is that you decouple your components (frontend and backend).. details
    • Jabsorb also has good (de)serialization package.. details
  • 3. frontend backend interchange format order edit comment add include byte: 5
    • The protobuf objects have serialization methods to bytes, it's very efficient and compresses really well.. details
    • EDIT added information asked by the comments -- thanks!. details
    • It's a JavaScript frontend, so json would be preferred.. details
    • In order to get the data from the backend to the frontend you have to use some data interchange format like JSON or XML .. details
    • It also helps to have "standard" persistence framework.. details
  • 4. solution leave box mapper submit single slight overhead browser prevent: 7
    • Or [Protocol Buffers]( /) since it's supported by almost any language, results in smaller serialized data and you don't even have to write a single line of code to parse / serialize it.. details
    • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader.. details
    • Interestingly the class it says it can't find is different: CODESNIPPET .. details
    • One last note : The object mapper is thread safe and having one static instance like in the example I just submitted will prevent you from having the slight instantiation overhead.. details
    • I also use it as the serialization for my RPC-style APIs for fairly high traffic systems, although I prefer using Protobuf for those when possible.. details
    • JAX-RS implementations support the type out of the box and it sounds like an easy solution to leave the rest to the browser.. details
    • The advantage of JSON is, that is fairly efficient compared to XML and well accepted.. details
  • 0. format mode play start dev include pbserializer exception follow store: 9
    • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.. details
    • Check out serialization/src/main/java/org/jbox2d/serialization/pb/PbSerializer.java [PbSerializer] and here is documentation on protobufs: .. details
    • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path.. details
    • I can run without problems: CODESNIPPET .. details
    • If play is started in production mode I do not have any errors.. details
    • This leads to the following error when running in dev mode (started with play run) CODESNIPPET .. details
    • I have been able to get it to work in dev mode if I put the source code for protobuf-java-format in my app folder.. details
    • NoClassDefFoundError is thrown when I try to use any static method from protobuf-java-format library.. details
    • Over the years I have tried quite a few options or serialization/deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here :-) Right now we are using JSON encoding almost exclusively for both Java-to-Java and JS-to-Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient).. details
  • 1. format service scalability loading xxxxx follow specific applications exception thing: 4
    • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).. details
    • Another very useful method to play around with when debugging is XXXXX.class.getProtectionDomain().getCodeSource().getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf-java-format is having a problem loading and also any class from protobuf-java-format.. details
    • Trying to covert any protobuf to JSON using CODESNIPPET .. details
    • By doing this you achieve following things: Make your services available to other (web-)applications and users because your service exposes a specific API/data exchange format that they can use.. details
Summaries of the opinions about com.google.protobuf using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON .
  • thanks for the answer .
  • In order to get the data from the backend to the frontend you have to use some data interchange format like JSON or XML .
  • The advantage of JSON is, that is fairly efficient compared to XML and well accepted .
  • The biggest advantage of applying this service oriented approach** to your own project is that you decouple your components (frontend and backend) .
  • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method .
  • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most) .
  • I also use it as the serialization for my RPC style APIs for fairly high traffic systems, although I prefer using Protobuf for those when possible .
  • (If the fact that I'm using a Java REST service instead of say, a servlet to upload the files is going to be the biggest slowdown, that's also a good answer!).
  • I am working with protobufs with the play framework 2 1 3 without issues .
  • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like google protocol buffers Also check out the Externalizable interface for custom serialisation .
  • In order to get the data from the backend to the frontend you have to use some data interchange format like JSON or XML .
  • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method .
  • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most) .
  • One last note : The object mapper is thread safe and having one static instance like in the example I just submitted will prevent you from having the slight instantiation overhead .
  • readable code architecture In short, which of the 3 formats mentioned above fits those requirements the best, given that I'm using a Java REST service on the backend?.
  • (If the fact that I'm using a Java REST service instead of say, a servlet to upload the files is going to be the biggest slowdown, that's also a good answer!).
  • JAX RS implementations support the type out of the box and it sounds like an easy solution to leave the rest to the browser .
  • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader .
  • Other things you can do is call class in each and get the classloader and fool around with getting the classloaders parents as well to see what the classloader heirarchy looks like .
  • In order to get the data from the backend to the frontend you have to use some data interchange format like JSON or XML .
  • The advantage of JSON is, that is fairly efficient compared to XML and well accepted .
  • The biggest advantage of applying this service oriented approach** to your own project is that you decouple your components (frontend and backend) .
  • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method .
  • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most) .
  • I also use it as the serialization for my RPC style APIs for fairly high traffic systems, although I prefer using Protobuf for those when possible .
  • readable code architecture In short, which of the 3 formats mentioned above fits those requirements the best, given that I'm using a Java REST service on the backend?.
  • (If the fact that I'm using a Java REST service instead of say, a servlet to upload the files is going to be the biggest slowdown, that's also a good answer!).
  • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader .
  • Other things you can do is call class in each and get the classloader and fool around with getting the classloaders parents as well to see what the classloader heirarchy looks like .
  • Actually, I disagree on your "scalability" and "maintenace" "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols) .
  • Over the years I have tried quite a few options or serialization deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here : ) Right now we are using JSON encoding almost exclusively for both Java to Java and JS to Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient) .
  • By doing this you achieve following things: Make your services available to other (web )applications and users because your service exposes a specific API data exchange format that they can use .
  • I can run without problems: CODESNIPPET JAVA4 .
  • Trying to covert any protobuf to JSON using CODESNIPPET JAVA2 .
  • This leads to the following error when running in dev mode (started with play run) CODESNIPPET JAVA3 .
  • If play is started in production mode I do not have any errors .
  • I have been able to get it to work in dev mode if I put the source code for protobuf java format in my app folder .
  • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path .
  • Another very useful method to play around with when debugging is XXXXX class getProtectionDomain() getCodeSource() getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf java format is having a problem loading and also any class from protobuf java format .
  • Actually, I disagree on your "scalability" and "maintenace" "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols) .
  • Over the years I have tried quite a few options or serialization deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here : ) Right now we are using JSON encoding almost exclusively for both Java to Java and JS to Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient) .
  • By doing this you achieve following things: Make your services available to other (web )applications and users because your service exposes a specific API data exchange format that they can use .
  • Trying to covert any protobuf to JSON using CODESNIPPET JAVA2 .
  • This leads to the following error when running in dev mode (started with play run) CODESNIPPET JAVA3 .
  • I have been able to get it to work in dev mode if I put the source code for protobuf java format in my app folder .
  • NoClassDefFoundError is thrown when I try to use any static method from protobuf java format library .
  • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path .
  • Another very useful method to play around with when debugging is XXXXX class getProtectionDomain() getCodeSource() getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf java format is having a problem loading and also any class from protobuf java format .
  • simplify the problem then take out protobuf java format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first .
  • Over the years I have tried quite a few options or serialization deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here : ) Right now we are using JSON encoding almost exclusively for both Java to Java and JS to Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient) .
  • Check out serialization src main java org jbox2d serialization pb PbSerializer java PbSerializer and here is documentation on protobufs: .
  • Trying to covert any protobuf to JSON using CODESNIPPET JAVA2 .
  • This leads to the following error when running in dev mode (started with play run) CODESNIPPET JAVA3 .
  • If play is started in production mode I do not have any errors .
  • I have been able to get it to work in dev mode if I put the source code for protobuf java format in my app folder .
  • NoClassDefFoundError is thrown when I try to use any static method from protobuf java format library .
  • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path .
  • Another very useful method to play around with when debugging is XXXXX class getProtectionDomain() getCodeSource() getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf java format is having a problem loading and also any class from protobuf java format .
  • simplify the problem then take out protobuf java format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first .
Summaries of the opinions about com.google.protobuf using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about com.google.protobuf using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Features:
  • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader.
  • If play is started in production mode I do not have any errors.
Documentation:
  • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like URL_http://code.google.com/apis/protocolbuffers/docs/overview.html [google-protocol-buffers] Also check out the URL_http://java.sun.com/j2se/1.3/docs/api/java/io/Externalizable.html [Externalizable] interface for custom serialisation .
  • Check out URL_https://code.google.com/p/jbox2d/source/browse/trunk/jbox2d- serialization/src/main/java/org/jbox2d/serialization/pb/PbSerializer.java [PbSerializer] and here is documentation on protobufs: URL_https://code.google.com/p/protobuf/ [ URL_https://code.google.com/p/protobuf/ ] .
Onlysentiment:
  • thanks for the answer.
  • N/A
Performance:
  • One last note : The object mapper is thread safe and having one static instance like in the example I just submitted will prevent you from having the slight instantiation overhead.
  • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).
Bug:
  • I am working with protobufs with the play framework 2.1.3 without issues.
  • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.
Usability:
  • The protobuf objects have serialization methods to bytes, it's very efficient and compresses really well.
  • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.
  • Features: 4
    1. general: 4
      • The best bet is to make sure this jar and the other protobuf jar end up in the same directory when you are running the app so they end up in the same classloader.. details
      • Interestingly the class it says it can't find is different: CODESNIPPET_JAVA6 .. details
      • EDIT added information asked by the comments -- thanks!. details
      • URL_http://jabsorb.org/ [Jabsorb] also has good (de)serialization package.. details
  • Documentation: 1
    1. general: 1
      • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like URL_http://code.google.com/apis/protocolbuffers/docs/overview.html [google-protocol-buffers] Also check out the URL_http://java.sun.com/j2se/1.3/docs/api/java/io/Externalizable.html [Externalizable] interface for custom serialisation .. details
  • Onlysentiment: 1
    1. general: 1
  • Performance: 4
    1. general: 4
      • One last note : The object mapper is thread safe and having one static instance like in the example I just submitted will prevent you from having the slight instantiation overhead.. details
      • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON.. details
      • performant and efficient data transfer.. details
      • The advantage of CODETERM5 is, that is fairly efficient compared to CODETERM6 and well accepted.. details
  • Bug: 1
    1. general: 1
      • I am working with protobufs with the play framework 2.1.3 without issues.. details
  • Usability: 19
    1. service: 1
      • The biggest advantage of applying this service oriented approach** to your own project is that you decouple your components (frontend and backend).. details
    2. rest: 3
      • JAX-RS implementations support the type out of the box and it sounds like an easy solution to leave the rest to the browser.. details
      • readable code/architecture In short, which of the 3 formats mentioned above fits those requirements the best, given that I'm using a Java REST service on the backend?. details
      • (If the fact that I'm using a Java REST service -- instead of say, a servlet -- to upload the files is going to be the biggest slowdown, that's also a good answer!). details
    3. general: 5
      • As a temporary solution this works, but I would like to know the correct way to deal with this problem.. details
      • Protobuf is very handy, and is designed to be highly performant (cheaper to process, smaller output) and very version tolerant but browsers are better at processing JSON.. details
      • The advantage of CODETERM5 is, that is fairly efficient compared to CODETERM6 and well accepted.. details
      • These are very useful when you want to include the services in your applications.. details
      • If you are not particularly tied to JSON, URL_http://code.google.com/p/protobuf/ [Protocol-Buffers] is worth checking out.. details
    4. json: 1
      • It's a JavaScript frontend, so json would be preferred.. details
    5. performance: 1
      • Under the hood this just uses java serialisation If your needs are performance sensitive (low latency, high throughput) you could use something like URL_http://code.google.com/apis/protocolbuffers/docs/overview.html [google-protocol-buffers] Also check out the URL_http://java.sun.com/j2se/1.3/docs/api/java/io/Externalizable.html [Externalizable] interface for custom serialisation .. details
    6. serialization: 4
      • What do you mean "my object writer would pass it"?Also, all you have to do is call build() on the world that you serialize, and then you can do something like "toByteArray()" or something like that, take a look at the protobuf javadoc for the best serialization method.. details
      • The protobuf objects have serialization methods to bytes, it's very efficient and compresses really well.. details
      • I made the serialization package for this reason :) I include serialization to protobufs, which is probably the best thing for you (it reduces the size the most).. details
      • I also use it as the serialization for my RPC-style APIs for fairly high traffic systems, although I prefer using Protobuf for those when possible.. details
    7. data: 2
      • Or [Protocol Buffers]( URL_http://code.google.com/p/protobuf /) since it's supported by almost any language, results in smaller serialized data and you don't even have to write a single line of code to parse / serialize it.. details
      • In order to get the data from the backend to the frontend you have to use some data interchange format like CODETERM3 or CODETERM4 .. details
    8. class: 1
      • Other things you can do is call class in each and get the classloader and fool around with getting the classloaders parents as well to see what the classloader heirarchy looks like.. details
    9. persistence: 1
      • It also helps to have "standard" persistence framework.. details
  • Performance: 1
    1. general: 1
      • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).. details
  • Documentation: 1
    1. general: 1
      • Check out URL_https://code.google.com/p/jbox2d/source/browse/trunk/jbox2d- serialization/src/main/java/org/jbox2d/serialization/pb/PbSerializer.java [PbSerializer] and here is documentation on protobufs: URL_https://code.google.com/p/protobuf/ [ URL_https://code.google.com/p/protobuf/ ] .. details
  • Features: 1
    1. general: 1
      • If play is started in production mode I do not have any errors.. details
  • Bug: 3
    1. general: 3
      • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.. details
      • I can run without problems: CODESNIPPET_JAVA4 .. details
      • This leads to the following error when running in dev mode (started with play run) CODESNIPPET_JAVA3 .. details
  • Usability: 9
    1. general: 9
      • simplify the problem then...take out protobuf-java-format and instead add code like Exception e new InvalidProtocolBufferException() to see if that works first.. details
      • Actually, I disagree on your "scalability" and "maintenace" / "change" points re protobuf: protobuf is specifically designed for scalability, with dense output (smaller than json etc), and cheap processing (especially compared to text protocols).. details
      • Another very useful method to play around with when debugging is XXXXX.class.getProtectionDomain().getCodeSource().getLocation() replace XXXXX with a class that exists in protobuf like that Exception class that your class is having no problem loading and protobuf-java-format is having a problem loading and also any class from protobuf-java-format.. details
      • Trying to covert any protobuf to JSON using CODESNIPPET_JAVA2 .. details
      • I have been able to get it to work in dev mode if I put the source code for protobuf-java-format in my app folder.. details
      • NoClassDefFoundError is thrown when I try to use any static method from protobuf-java-format library.. details
      • I am using the methods from the protobuf library without problems elsewhere, so I know they are being included in the class path.. details
      • By doing this you achieve following things: Make your services available to other (web-)applications and users because your service exposes a specific API/data exchange format that they can use.. details
      • Over the years I have tried quite a few options or serialization/deserialization, including JSON, XML, SOAP, protobuf and some others I am embarrassed to name here :-) Right now we are using JSON encoding almost exclusively for both Java-to-Java and JS-to-Java transfers, and even for storing internal data (unless the amount of binary data makes the JSON format too inefficient).. details