Hi,
I'm looking at using the Haskell implementation of protocol buffers in a
project of mine, and I'm running into somewhat of a dearth of Haskell
projects that actually use hprotoc and the related protocol buffer
libraries. Specifically, to get started, I just want to integrate the
building of
ok, just like i thought.
thanks for the info
On Mar 11, 8:35 pm, Kenton Varda ken...@google.com wrote:
The tests obviously can't run when cross-compiling, so this is expected.
You should manually run protobuf-test on the target architecture to make
sure it works. The other tests probably
Hi,
Actually I am trying this on 2 different boxes: (1) Solaris 10 and (2)
Nexenta.
On (1) the gcc version was (gcc (GCC) 3.4.6)
On (2) the gcc version was (gcc version 4.2.3 (Ubuntu
4.2.3-2nexenta7) )
... And neither has worked.
I am really sorry for the confusion. Here is the excerpt from
Hi,
Could someone please help and tell me waht is wrong with makefile ?
here is a part of it
CXX = g++
CXXFLAGS = -Wall -ansi -pedantic -g
INCLUDES := -I/home/apollo/protobuf-2.2.0/include
ifeq ($(shell uname),SunOS)
LIBS = -lsocket -lnsl
endif
all: client
client: client.cpp data_exge.pb.cc
Hi,
I am trying to send a proto over a socket, but i am getting
segmentation error. Could someone please help and tell me what is
wrong with this?
file.proto
message data{
required string x1 = 1;
required uint32 x2 = 2;
required float x3 = 3;
}
client.cpp
...
//
Hi,
I am trying to send a proto over a socket, but i am getting
segmentation error. Could someone please help and tell me what is
wrong with this?
file.proto
message data{
required string x1 = 1;
required uint32 x2 = 2;
required float x3 = 3;
}
client.cpp
...
//
On what line do you get the error?
On Fri, Mar 12, 2010 at 9:29 AM, mk apollo...@gmail.com wrote:
Hi,
I am trying to send a proto over a socket, but i am getting
segmentation error. Could someone please help and tell me what is
wrong with this?
file.proto
message data{
required
You're trying to send the raw C++ memory representation of a protocol object
send(socket, data_snd, sizeof(data_snd), 0)
That doesn't work. And is the reason why protocol buffers are there in
the first place: they provide serialization techniques.
You need to use the serialization methods that
Wait.
On Fri, Mar 12, 2010 at 9:29 AM, mk apollo...@gmail.com wrote:
Hi,
I am trying to send a proto over a socket, but i am getting
segmentation error. Could someone please help and tell me what is
wrong with this?
file.proto
message data{
required string x1 = 1;
I've generated all my protos with -p:detectMissing flag which works
fine.
However, all the optional strings get generated as
public string mystring {
get { return _myString ?? ; }
As a result, empty strings are being transmitted over the wire. This
requires me to manually edit the
On Thu, Mar 11, 2010 at 1:52 PM, Igor Gatis igorga...@gmail.com wrote:
*- Why did you eliminate the builder pattern?*
To save jar space. J2ME environment is pretty restricted. Many devices have
a few kilo bytes size limit (e.g 128K, 256K). An empty class adds about 200
bytes to jar file. The
The work is going slowly because the Python C extension API has lots of
subtle quirks. The good news is that Google has Python implementation
experts who are reviewing the code. But this is 20% work for everyone
involved (i.e. not their real jobs) so it will take awhile.
My hope is that we'll
On Fri, Mar 12, 2010 at 10:20, mk apollo...@gmail.com wrote:
Thanks for reply !!
Could you please give an example? I tried several ways from this
morning but as I am a new user of protbuf, I don't see what way to
follow ... Thanks!
Have a look at the documentation, it is full of examples
thanks for reply
Could you please give or send me a small exp on how to serialize and
deserialize proto?
thanks again!
On Mar 12, 6:37 pm, Henner Zeller henner.zel...@googlemail.com
wrote:
You're trying to send the raw C++ memory representation of a protocol object
send(socket, data_snd,
myMessage.getSubMessage().setFoo(1);
If they haven't previously called setSubMessage(new SubMessage()) then this
code will actually modify the shared default instance of SubMessage which
could cause all sorts of bugs around the system. Have you considered how to
avoid this problem?
I think I have a solution for the readonly messages.
Message.java now includes the following header:
public abstract class Message {
private boolean readOnly;
protected Message(boolean noInit) {
this.readOnly = true;
}
public Message() {}
protected void assertNotReadOnly() {
if (readOnly) {
I've started a small project at
https://code.google.com/p/protobuf-jerpc/which contains an
implementation of a protoc plugin that outputs essentially
the same classes etc that the current generic services mechanism outputs
(but in a different namespace).
Also in the project is a very simple C++
Looks like the word which got appended to the end of the URL in your
posting.
Should be https://code.google.com/p/protobuf-jerpc/
On Mar 12, 9:17 pm, Andrew Kimpton awkimp...@gmail.com wrote:
I've started a small project
athttps://code.google.com/p/protobuf-jerpc/whichcontains an
This may solve the problem but adding code to every setter may have a
significant cost. It's harder to inline the setter this way. But it's hard
to say exactly what the cost will be without some sort of benchmarks.
On Fri, Mar 12, 2010 at 12:12 PM, Igor Gatis igorga...@gmail.com wrote:
I
My experience with J2ME says performance is not the most important feature
for the majority of the applications. Trust me when I say JAR size is the
one people care the most.
Besides, the extra cost is a method call + condition check, that's fairly
cheap. Depending on the compiler and/or
Hi,
Could someone please help me with serialization/deserialization
classes defined in .proto (protobuf). here is an exp that I am trying
to build:
file.proto
message Data{
required string x1 = 1;
required uint32 x2 = 2;
required float x3 = 3;
}
message DataExge {
Hi,
Could someone please help me with serialization/deserialization
classes defined in .proto (protobuf). here is an exp that I am trying
to build (see server where I get error):
file.proto
message Data{
required string x1 = 1;
required uint32 x2 = 2;
required float x3 =
Please read the tutorial:
http://code.google.com/apis/protocolbuffers/docs/cpptutorial.html
On Fri, Mar 12, 2010 at 7:39 PM, mk apollo...@gmail.com wrote:
Hi,
Could someone please help me with serialization/deserialization
classes defined in .proto (protobuf). here is an exp that I am
Thanks for reply
As I said before, I don't have any experience in writing serialization/
deserialization codes
I read and followed the tutorial you referred to and still I am the
error. Actually, the error is when the server calls
serialize(dataexge)
Any help would be very appreciated.
Thanks
Reconsider having a look at your code and ask yourself the following
questions
- what are the input/output streams connected to. Is it the socket ?
- what do you send over the socket ? Is it the data coming from a
SerializeTo*() method of the protocol buffer ?
Trial and Error programming just
25 matches
Mail list logo
