Hi Stephen, The goal is to have a complete userspace stack, i.e., a session layer accessible over VPP’s binary API, a transport layer, a POSIX-like wrapper library for interacting with the stack and a shared memory mechanism to pass data between apps and VPP. We have support for pluggable transports but the only one actively being developed right now is TCP. The wrapper library (VCL) will soon be published, but Keith can tell you more about it.
Florin > On Aug 9, 2017, at 7:55 AM, STEPHEN PETRIDES <sdp...@scarletmail.rutgers.edu> > wrote: > > Hi All, > > I came across this exchange > (https://www.mail-archive.com/vpp-dev@lists.fd.io/msg03112.html > <https://www.mail-archive.com/vpp-dev@lists.fd.io/msg03112.html>) in the > mailing list and wanted to learn more about what features of the stack are > available currently and what is still being developed. > > For the internal/external apps mentioned, how do these work and what features > are currently supported? > > For the wrapper library being developed, what will this look like? Will there > be an API or interface for endpoint applications? > > Thank you. > > -- > Stephen > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
