Best approach for small distributed C ++ applications

I am working on distributing a standalone application. Each application instance must be able to send and receive requests.

Requirements:

  1. Language - C ++
  2. The scale is small. May be 5 copies at a time
  3. Platform independence
  4. The amount of data transferred is expected to be high (source images in the worst case)

I do not want to use RPC because it needs a registry service. I think CORBA and SOAP will be too expensive. I somehow decided to use my own protocol, but I just want to hear if something is better.

Thanks.

+5
source share
6 answers

, ++, -, .

+6

MPI , , , Corba ..
, , !

+5

http POST?

  • , ( , POST), , http-.
  • ( apache iis)
  • ( )
  • (- )
  • http- (xp ).
  • / .
  • firefox.
  • , - .
  • , .
  • .
  • .
+4

HTTP- -, . , - - Mongoose.

+3

Spread Toolkit. , C, ++ , . , ( ).

- :

Spread - , , . , . .

, , . .

Spread , , , , , .

, Spread:

  • .
  • , API .
  • , .
  • .
  • .
  • , , .
  • , .
  • .
  • .

, , , , , : . , , , , , ; , , , , , TCP, .

(, . .)

+3

I would suggest you evaluate RCF from deltavsoft, it seems like a good fit, as it is designed for a C ++ application, and it's free.

http://deltavsoft.com/w/

+1
source

All Articles