The POCOPRO C++ Frameworks include the open source POCO C++ Libraries and add the Remoting and Open Service Platform (OSP) frameworks under commercial source code license. Professional support is included.
macchina.io EDGE adds IoT-specific services and communication protocols implemented
with Remoting and OSP frameworks. It also includes a JavaScript engine for simplified
IoT edge application development. A C++ bridging framework also based on Remoting
makes it easy to access C++ services from JavaScript.
Visit macchina.io/edge for more information.
macchina.io REMOTE is a secure remote access solution for IoT devices. It consists
of a device agent and SDK based on the POCO C++ Libraries and a server that is
also built with POCO, Remoting and OSP.
Visit macchina.io/remote for more information.
Web services, REST APIs and microservices have significantly changed the way complex software systems are designed, built and deployed. POCOPRO Remoting makes these technologies and concepts available to C++ developers.
Remoting for C++ is a web services and remote method call
framework for C++. Remoting supports different communication
protocols. This includes JSON-based REST APIs, JSON-RPC,
SOAP and a highly efficient binary protocol.
Remote services are implemented as C++ classes, annotated
with special comments.
The Remoting code generator takes care of the rest.
There is no need to maintain a separate interface definition
using an interface definition language (IDL).
Remoting also includes a tool for generating C++ code from WSDL 1.1 (document/literal wrapped) and XML Schema (XSD) documents. This makes it possible to build C++ clients for SOAP 1.1 and 1.2 web services built with Java, Microsoft .NET, or other middleware technologies.
Easily communicate between different hardware and operating system platforms. Or clients and servers built in other programming languages and environments such as Java or .NET.
Remoting supports sockets, HTTP, REST, JSON-RPC and SOAP. Thanks to a flexible and modular design, other protocols can be added by implementing a new protocol library.
The RemoteGen code generator generates protocol independent, human-readable communication code from annotated C++ header files.
All standard C++ types and some STL collection types (including enumerations, std::string, std::vector, std::set and std::multiset), as well as user-defined classes and structures are supported as method arguments and return types.
Implement REST API endpoints in C++. Supporting different forms of parameter passing (path, query string, header, body, JSON) as well as authentication, CORS, etc. Or generate client code to call external REST APIs.
Implement microservices in C++ exposing REST APIs for best interoperability. Or use the super efficient binary transport protocol for communication between C++ applications.
Generate C++ client and server code for SOAP web services from WSDL documents. Implement SOAP 1.1/1.2 web services in C++ that can be called from Java and .NET WCF applications with support for MTOM, HTTPS, HTTP compression (gzip content encoding) and HTTP Basic and Digest authentication.
Support for events in remote interfaces enables implementation of server-pushed asynchronous notifications or publish-subscribe messaging patterns.
The following code snipped shows an example for how to define a RESTful API with Remoting. This definition is specific to the Remoting REST transport. Note how the method names correspond to HTTP methods. Also note the special comments. The Remoting code generator (RemoteGen) parses these definitions and generates C++ code that implements serialization, deserialization and remote invocation.
//@ serialize
struct User
{
std::optional<std::string> name;
std::optional<std::string> password;
std::optional<std::set<std::string>> permissions;
std::optional<std::set<std::string>> roles;
};
//@ remote
//@ path="/api/1.0/users"
class UserCollectionEndpoint
{
public:
User post(const User& user);
/// Create a new user.
//@ $maxResults={in=query, optional}
//@ $start={in=query, optional}
std::vector<User> get(int maxResults = 0, int start = 0);
/// Return a list of user objects, starting with
/// the given start index, and return at most
/// maxResults items.
};
//@ remote
//@ path="/api/1.0/users/{name}"
class UserEndpoint
{
public:
//@ $name={in=path}
User put(const std::string& name, const User& user);
/// Update a user (calls patch()).
//@ $name={in=path}
User patch(const std::string& name, const User& user);
/// Update a user.
//@ $name={in=path}
User get(const std::string& name);
/// Retrieve a user by name.
//@ $name={in=path}
void delete_(const std::string& name);
/// Delete a user.
};
The following code snipped shows an example for a remote methods-based service that can use the efficient binary Remoting transport over sockets or HTTP, the JSON-RPC or the SOAP transport. Again, note the special comments. The Remoting code generator (RemoteGen) parses these definitions and generates C++ code that implements serialization, deserialization and remote invocation.
//@ serialize
struct User
{
std::string name;
std::optional<std::string> password;
std::optional<std::set<std::string>> permissions;
std::optional<std::set<std::string>> roles;
};
//@ remote
class UserManager
{
public:
void addUser(const User& user);
/// Create a new user.
void updateUser(const User& user);
/// Update a user.
User getUser(const std::string& username);
/// Retrieve a user by name.
//@ $maxResults={optional}
//@ $start={optional}
std::vector<User> getUsers(int maxResults = 0; int start = 0);
/// Return a list of user objects, starting with
/// the given start index, and return at most
/// maxResults items.
void deleteUser(const std::string& username);
/// Delete a user.
};
Today's applications are becoming ever more complex. A large part of this complexity stems from the need to support different configurations, e.g. for different devices, operating system environments or customer needs. Huge monolithic applications like the ones developed in the past do not (or only at an enormous cost) provide the necessary flexibility required today.
Open Service Platform (OSP) enables the creation, deployment and management of dynamically extensible, modular applications, based on a powerful plug-in and (nano-) services model. Applications built with OSP can be extended, upgraded and managed even when deployed in the field. At the core of OSP lies a powerful software component (plug-in) and services model based on the concept of bundles. A bundle is a deployable entity, consisting of both executable code (shared libraries) and the required configuration, data and resource files.
Bundles extend the functionality of an application by providing certain services. A central Service Registry allows bundles to discover the services provided by other bundles. Bundles can be installed, upgraded, started, stopped or removed from an application (programmatically, or using a web- or console based administration utility) without the need to terminate and restart the application.
This component-based architecture of OSP addresses an increasing problem in software development: The large number of application configurations that need to be developed and maintained. The standardized OSP component architecture simplifies this configuration and deployment process significantly.
Create dynamically extensible C++ applications based on a powerful plug-in/component and services architecture. Combine executable code (shared libraries), configuration files and other resources like web pages or images in bundles - easily manageable deployment units.
Install, start, stop, upgrade or uninstall an application's bundles dynamically, at run-time. Without the need to restart the entire application.
Automatically manage version dependencies between bundles. OSP makes sure that all dependencies are satisfied and that bundles are started or stopped in correct order.
Provide and find services in an application through a central ServiceRegistry. Dynamically react to availability of services through events or ServiceListener objects.
Manage an application's bundles through a built-in web-based Bundle Administration Utility or through an extensible console based shell (CLI) administration service.
An integrated web application server enables powerful dynamic C++ web applications. Routing, sessions, authentication, access permissions and CSRF protection can be configured using metadata and are handled by the framework, without the need for extra code.
Bundles can be cryptographically signed. Make sure bundles installed in your system come from a known publisher and have not been tampered with.
Readily available services for user authentication and authorization, settings, preferences and configuration data, extension points, database access, email, network environment change detection, web events, etc.
Built-in authentication and authorization framework with accounts database, two-factor authentication (OTP), LDAP integration and flexible roles and permissions-based access control.
The POCOPRO C++ Frameworks and macchina.io EDGE are available under a commercial source code license.
Please contact us for licensing and purchasing inquiries.
Please contact us for a quote, to order licenses, or with any questions regarding the POCOPRO C++ Frameworks, macchina.io EDGE or macchina.io REMOTE.
Download a free trial version of the POCOPRO C++ Frameworks to try out the included demo applications or build your own programs.
Please read the Getting Started Guide before downloading and installing the software. This document contains valuable information that will help you get the best out of the POCOPRO C++ Frameworks, including setup instructions and tips to get you started.
The Windows trial version is available for Visual Studio 2017, 2019 and 2022. Only 64-bit builds
are supported by the trial version. The full version supports both 32-bit and 64-bit builds.
Need an trial version for a different platform? Please let us know.
A license file is required for running applications (including the samples) built with the POCOPRO C++ Frameworks trial version. Receive the license file via email by filling out the form on the right.
No license file will be required once you purchase a source code license.
Requests for license files are processed automatically. You should receive the license file via email within a few minutes after submitting the form. If not, please check your junk mail folder.
An evaluation version of macchina.io EDGE, licensed under the GPLv3, is available on GitHub.
Please note that this version only contains a subset of all features available in the full, commercially-licensed version.
To get access to the full-featured version of macchina.io EDGE for evaluation purposes, please contact Applied Informatics.