1. But if the back-end wants to make a remote procedure call to a mobile
device, so the back-end is the client and the mobile device is the
server, the mobile device must open the connection in some way before,
as the mobile device's IP is a dynamic IP. This is, what I thought by
"register" to the back-end.
4. You are right here. Does Thrift supports SSL to secure a service?
Best regards,
Thomas
Am 01.03.2016 16:38 schrieb j.barrett Strausser:
1. Clients don't register themselves with a server. Clients make remote
procedure calls to a Server. Sometimes a client can also be a server.
2. I run thrift over 4G with a both the http and socket transport.
I've
not encountered any issues. I have a custom python transport pool,
that
heals itself when the socket is closed. Alternatively, you can create a
transport per request. The overhead is probably low enough for you.
3. I have had issues with large files over Thrift. Almost everyone
will
suggest you use chunked-messages. I have very large files to upload
and I
needed to be friendly on my 4G costs by not sending chunks that had
already
been sent so we had to work around that. Agreed that some sort of Rsync
like ability over Thrift would be useful.
4. If using 3G, I assume you *do not* have a static IP on the client
side?
I would think about your security model a bit.
-b
-b
On Mon, Feb 29, 2016 at 2:26 PM, <[email protected]> wrote:
Hi,
I try to evaluate if Thrift is a good choice for my use case where the
clients are connected via mobile network (3G) to the server. The
communication pattern is quite simple, just client <-> server, but
there is
no communication between the clients. But there are some points, where
I'm
not sure if Thrift can handle them well:
- bidirectional communication: after a client has registered itself to
the
server, the client may call an rpc on the server and vice versa. Does
Thrift supports WebSockets? I'm not a big friend of http long polling.
- Due to 3G the connection will come and go. Any problem for Thrift?
- The typical rpc will transfer just some bytes of date, something
like
send current GPS position to server or push some message to the
client. But
it is also required to send a binary file (size between 250k to 5m)
from or
to the server. Any limitations here? Is there something like FileMQ
for
ZeroMQ out there for Thrift?
Has anyone realized a similar project with thrift?
Best regards,
Thomas
