search

dingykhan1 / scoop

Automatically exported from code.google.com/p/scoop
GNU Lesser General Public License v3.0
0 stars 0 forks source link

How to call it from other projects #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What i don't understand is using scoop in existing projects.

How can i push data and get data, if i want to call from existing project?

SCOOP cannot be used as an RPC it seems , have to integrate with some other RPC 
Libraries?

Original issue reported on code.google.com by phyo.arkarlwin on 6 Mar 2013 at 3:15

GoogleCodeExporter commented 8 years ago 
Hello M. Arkarlwin,

Effectively, SCOOP isn't meant as an RPC service. Trying to use it like so 
would result in a fight against the future API.

The purpose of SCOOP is to easily integrate into serial projects executing 
repeatedly tasks while varying its data. One of our goals is to ease the burden 
of communication upon the user. This sadly means that explicit communication 
(pushing, getting, serialization, encapsulation, load balancing) isn't 
available.
You can check our examples for ideas of usage we provide. They are available 
here: https://code.google.com/p/scoop/source/browse/#hg%2Fexamples .

On a limit use case, you could use SCOOP as a launcher to execute os.system() 
calls to launch parallely a third party program (written in C, for instance). 
If you intend this kind of usage on Python programs, you may be interested in 
the Fabric project which may better suit your needs ( http://fabfile.org ) or a 
parallel SSH project (pdsh, for example).

If you need a RPC service based on the same technology we use, you could check 
zerorpc-python (https://github.com/dotcloud/zerorpc-python).

Original comment by yannickh...@gmail.com on 14 May 2013 at 8:36