Download Latest Version tcelib.0.2.0_py_as_20120919.tgz (74.1 kB)
Email in envelope

Get an email when there's a new version of TCE

Home / tcelib-py_0.1.0
Name Modified Size InfoDownloads / Week
Parent folder
utils.py 2012-09-11 4.9 kB
README 2012-09-10 1.9 kB
test_s.py 2012-09-10 1.9 kB
test_c.py 2012-09-10 1.9 kB
tcelib.py 2012-09-10 10.4 kB
tce1.txt 2012-09-10 889 Bytes
tce2py.py 2012-09-10 24.2 kB
parser.out 2012-09-10 17.8 kB
parsetab.py 2012-09-10 5.2 kB
network.py 2012-09-10 11.3 kB
mylex.py 2012-09-10 6.7 kB
message.py 2012-09-10 3.3 kB
lexparser.py 2012-09-10 3.8 kB
errbase.py 2012-09-10 812 Bytes
app.py 2012-09-10 39.3 kB
Totals: 15 Items   134.2 kB 0
tce
--------------
TINY COMMUNICATION ENGINE

https://sourceforge.net/projects/adoggie-tce/files/tcelib/


#scott  shanghai china
#86-13916624477 qq:24509826 msn: socketref@hotmail.com
#

traits:
=======
1. idl maping support py,c++,java,actionscript
2. flexible rpc ,oop
3. offer rpc calltypes:
    normal-call (twoway) - user initial call and wait until  return ,thread will be blocked .
    oneway-call        - return immediately after initialing call
    timeout-call       - specify waiting time ,thread  will be  unbocked if timeup.
    async-call         -  thread is unblocked,return value  be passed into sink (like callback)
    reversed-call      - establishing one connection,two endpoints can setup owner service interfaces for another.
                通常互联网应用时,服务器与客户机链接必须由客户机发起,客户机发起者可以rpc方式调用服务器上的servant服务
                reversed-call实现了了在客户机建立的连接上,由服务器发起rpc服务请求到客户机上,同样的客户机提供servant对象
                基于socket流消息到Rpc函数接口级调用的差别


steps:
=======
1. create your idl, to see <tce1.txt>
2. compile idl
    python tce2py.py
    it will create app.py
3. execute test_s.py , test_c.py
    illustrating how to rpc

requirements:
==============
1.python 2.6 above
2.ply 3.4


enjoy!


revisions:
===============
2012.9.10 21:35  v0.1.0
1. fixed bugs about reverse-call, oneway call ...
2. testing all api,it's okay

docs:
------
1. idl intr
    struct like c
    builtins: byte,char,short,int,long,float,double,string,bool
    containers:  sequence<type>  as array ( std::vector<> in c++)
                dictionayr<type1,type2> as hash (std::map<>  in c++)
    interfaces : include some callable funcitons in service end.







Source: README, updated 2012-09-10