Does anyone have a good practical use of descriptors? I'm trying to
figure out why these would be useful. It seems to me that when you
access the descriptor class, you're using the very class that defines
the methods described by the descriptor.
What can you do with a ServiceDescriptor? Is there a
DynamicServiceFactory similar to the DynamicMessageFactory where you
can instantiate a service when all you have is a ServiceDescriptor, or
some other equivalent way of doing it?
Thanks!
--~--~-~--~~~---~--~~
not provide RPC.
On Mon, Jun 29, 2009 at 10:15 AM, rthompson.dtisoft@gmail.com
rthompson.dtisoft@gmail.com wrote:
What can you do with a ServiceDescriptor? Is there a
DynamicServiceFactory similar to the DynamicMessageFactory where you
can instantiate a service when all you have
More specifically the service_reflection class.
On Jun 30, 9:26 am, rthompson.dtisoft@gmail.com
rthompson.dtisoft@gmail.com wrote:
Is there a C++ equivalent to
http://code.google.com/apis/protocolbuffers/docs/reference/python/goo...
?
which is used to create protocol service
.
But this is not an RPC implementation. You still have to add your own
networking layer.
On Tue, Jun 30, 2009 at 9:26 AM, rthompson.dtisoft@gmail.com
rthompson.dtisoft@gmail.com wrote:
Is there a C++ equivalent to
http://code.google.com/apis/protocolbuffers/docs/reference/python/goo
() and GetResponsePrototype() return
DynamicMessages, and have CallMethod() just call the RpcChannel's
CallMethod().
On Tue, Jun 30, 2009 at 2:03 PM, rthompson.dtisoft@gmail.com
rthompson.dtisoft@gmail.com wrote:
Right, but I'm importing a .proto file at runtime using the Importer
class
DynamicServiceFactory-New(MyRpcOne,MyRpcTwo,...)
This type of functionality doesn't appear to exist. Is there an
alternate way to implement this type of functionality?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group,
const google::protobuf::Descriptor* pDescriptorResponse =
m_pFileDescriptor-FindMessageTypeByName( SomeMessage );
const google::protobuf::Message* pConstMessageResponse =
m_pMessageFactory-GetPrototype( pDescriptorResponse );
SomeMessage* pSomeMessage
I ran Valgrind on our application and found quite a few possibly
lost bytes traces. Here is an example of one
==1473==at 0x40263A0: operator new(unsigned int)
(vg_replace_malloc.c:214)
==1473==by 0x4370EB8:
