ligang/vpp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
509 Commits 30 Branches 141 Tags
c4cb44c05d121da2e0f0ccd39d5e1bf470731a85
Commit Graph

4 Commits

Author SHA1 Message Date
Tibor Sirovatka
071d610dc4 Changed JVPP interface for construction and connectivity 
Simplified construction, autoconnected; possible connect/close
See updated sample test cases with changed interface usage

Change-Id: Ib53e855880bc414868aa2b9bb8f5df086917e375
Signed-off-by: Tibor Sirovatka <tsirovat@cisco.com>
 2016-05-23 06:25:05 +00:00
Tibor Sirovatka
c288066921 JVPP - null checks changed to Objects.requireNonNull usage 
Review changes incorporated

Change-Id: Ia04b62144a0d3643095b518db538c7eb5137c048
Signed-off-by: Tibor Sirovatka <tsirovat@cisco.com>
 2016-05-12 03:15:23 +00:00
Marek Gradzki
d85036fd6b HONEYCOMB-10: jVpp - the new java API. C code and jar file generation 
Added comments generation for C and Java files.

Change-Id: Ifb670a5592eb871bfe68804f0a8d8f9b5b14f00a
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Signed-off-by: Ed Warnicke <eaw@cisco.com>
 2016-05-02 20:58:54 +00:00
Maros Marsalek
45a42b5d7f HONEYCOMB-10: jVpp - the new java API. Java code generation 
The old japi has two main drawbacks:

* it is not fully generated (requres manual coding for
every new api call that returns data other thanstatus code)

* it is not asynchronous from Java perspective (requires
active wait loops - big overhead due to JNI boundary being
crossed lots of times).

The new api is lightweight (fully generated except for connect,
disconenct and ping) and truly asynchronous (uses callbacks,
utilities that offer java.util.concurrent.Future interface
are also provided).

Change-Id: I531080ef651e8a74f19210490c71d161221ab600
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Signed-off-by: Ed Warnicke <eaw@cisco.com>
 2016-05-02 08:46:21 -05:00