2:49 p.m.
Hi,
Once we have the x-protocols data access in place, do you see any issues with this
approach:
- hotrod java client + Avro writes an "Person" object
- mechached C++ client reads the binary representation from the server and deserialize it
with Avro into a C++ "Person" object
- would whit work with REST as well?
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
4:31 p.m.
On 4 Apr 2013, at 13:49, Mircea Markus <mmarkus(a)redhat.com> wrote:
Hi,
Once we have the x-protocols data access in place, do you see any issues with this
approach:
- hotrod java client + Avro writes an "Person" object
- mechached C++ client reads the binary representation from the server and deserialize it
with Avro into a C++ "Person" object
Yes, it should. And good idea, this will help us test cross-platform without a
requirement for more Hot Rod clients at this stage.
- would whit work with REST as well?
Not sure - I presume so, if Avro-serialized streams can then be base64-encoded/decoded.
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
4:38 p.m.
On 4 Apr 2013, at 15:31, Manik Surtani wrote:
> Once we have the x-protocols data access in place, do you see any
issues with this approach:
> - hotrod java client + Avro writes an "Person" object
> - mechached C++ client reads the binary representation from the server and
deserialize it with Avro into a C++ "Person" object
Yes, it should. And good idea, this will help us test cross-platform without a
requirement for more Hot Rod clients at this stage.
+1
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
10:12 a.m.
On Apr 4, 2013, at 2:49 PM, Mircea Markus <mmarkus(a)redhat.com> wrote:
Hi,
Once we have the x-protocols data access in place, do you see any issues with this
approach:
- hotrod java client + Avro writes an "Person" object
- mechached C++ client reads the binary representation from the server and deserialize it
with Avro into a C++ "Person" object
^ Hmmm, any Avro work I did was based around basic types and collections of basic types.
For custom types, Google Protocol buffers probably better which allows you to define
structure of types via .idl files and generate the corresponding code for C/Java/Python?
Also, have not really looked at the feasibility of Avro marshaller for C/C++.
- would whit work with REST as well?
^ As long as the client code (whatever language that is) calling REST can transform the
payload, then yes.
Cheers,
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
4303
days inactive
4307
days old
infinispan-dev@lists.jboss.org
3 comments
3 participants
participants (3)
-
Galder Zamarreño -
Manik Surtani -
Mircea Markus