Open Source XML-RPC Software

The portable Universal Plug and Play (UPnP) SDK provides support for building UPnP-compliant control points, devices, and bridges on several operating systems. The main repository is at GitHub in https://github.com/pupnp/pupnp. This is just a clone repository for legacy reasons. Old SourceForge repo: git://pupnp.git.sourceforge.net/gitroot/pupnp/pupnp

Finagle is an extensible RPC system for the JVM, used to construct high-concurrency servers. Finagle implements uniform client and server APIs for several protocols, and is designed for high performance and concurrency. Most of Finagle’s code is protocol agnostic, simplifying the implementation of new protocols. Finagle is written in Scala, but provides both Scala and Java idiomatic APIs. Finagle is a protocol-agnostic, asynchronous RPC system for the JVM that makes it easy to build robust clients and servers in Java, Scala, or any JVM-hosted language. We set out to develop a single implementation of the basic components of network servers and clients that could be used for all of our protocols. Finagle is a protocol-agnostic, asynchronous Remote Procedure Call (RPC) system for the Java Virtual Machine (JVM) that makes it easy to build robust clients and servers in Java, Scala, or any JVM-hosted language.

NOTE: we moved to http://exificient.github.io !!! The Efficient XML Interchange (EXI) format is a very compact representation for the Extensible Markup Language (XML) Information Set that is intended to simultaneously optimize performance and the utilization of computational resources. Besides the EXI library EXIficient provides a command-line interface (CLI, see com.siemens.ct.exi.cmd.EXIficientCMD) and a graphical user interface (GUI, see http://exificient.sourceforge.net/exificient.jnlp)

Vexi is a rich GUI platform for creating desktop-like Internet or intranet applications using an intuitive XML/JavaScript API and an extensible widget set with themes, JSON support. Communicate with servers using XMLRPC/SOAP/REST and runs on Java.

Start Building Rich Internet Applications Rapidly. OpenWebStudio (OWS) is a robust tool for building data bound forms, modules, utilities and more. Anyone, anywhere can create bullet proof solutions quickly.

XINS is an open-source Web Services technology, supporting SOAP, XML-RPC and REST. It consists mainly of an XML-based specification format and a Java-based implementation framework.

It is a lightweight API to invoke web services (RMI, CORBA, WebService (SOAP), XML-RPC, EJB, Hessian, Burlap, REST, ...), how simple Java Object calls. You can integrate Crispy in a Service Oriented Architecture (SOA) or in a Rich Client Platform (RCP).

Aria2Web is a PHP- and Javascript-based application that allows you to control the excellent and lightweight "aria2" over the web. That way you can use it as a download manager.

Porcupine is an open-source Python based web application server that provides front-end and back-end revolutionary technologies for building modern data-centric Web 2.0 applications.

Omega IRC Security Services - is a *nix based, modularized security services coded in C. Which supports multiple IRCd protocols.

A P2P overlay construction toolkit, which supports routing algorithm researchers in addition to application developers. It provides multiple routing (DHT) algorithms such as Chord, Kademlia, Koorde, Pastry and Tapestry, and a distributed environment emu

The PRAjax class can be used to reflect PHP code into JavaScript and Ajax methods and vice-versa. PHP objects can be used in JavaScript trough Ajax calls, both properties and (registered) functions.

C++ production ready implementation of Scott Seely's Simple SOAP RPC code. OS neutral, HTTP transport, XML validation, envelope parsing, RPC dispatching, extendable data types, fault generation and a extendable test suite useful for release validation. Now builds on newer versions of Linux.

XML is intolerant of errors. This program will automatically salvage XML files by finding the first XML error, then truncating a configurable number of characters before the error and finally using the great xmllint to recover the xml file by automatically adding the correct end tags. The program starts with a default of 50 characters truncation. This truncation value may need to be changed if the truncation happens in the middle of a complex tag as xmllint may not know how to recover the file correctly. Additionally some extra text or data may be recoverable by changing the truncation amount to less than 50 characters.The extra truncation is needed in the first place because the XML validator used is not able to perfectly identify where the XML corruption begins and will often not flag the corruption for several characters after it begins.

A PHP implementation of the XML-RPC web RPC protocol. Extra modules provide support for the JSON and JSONRPC protocols. A javascript version of the library is also available.

The APIlity PHP Library provides an object-oriented way to easily access and manage the Google AdWords API from within PHP. This comes along with an abstraction from the SOAP and WSDL details.

Lightweight XML processor; XML-POJO mapping via Java5 annotations or DTD; Preprocessing of XML documents using expression language; Binary XML; RMI friendly XML; JSON format support; XML marshall/unmarshall; HTML as XML parser; Swing XML Viewer

This is an archive of the PowerBlog blogging desktop software application. PowerBlog is no longer supported as of 2005 and stopped working when incompatibilities came with .NET Framework v2 and Internet Explorer (which was used for WYSIWYG HTML editing). PowerBlog was a powerful and intuitive Windows desktop blogging application. One could post blog entries to an XML-RPC/Blogger API host, FTP host, or other host. It was extensible using .NET assemblies or by using VBScript/JScript scripts. It had an Outlook-style article browsing interface. PowerBlog's closest competitor was w.Bloggar until Microsoft Live Writer was released, which made PowerBlog an irrelevant product. If you are curious about PowerBlog's author and what he is up to, visit http://www.jondavis.net/techblog Feel free to send Jon a message at jon -AT- jondavis-dot-net (<< anti-spam) asking him what he's been up to with blogging solutions lately.

An XMLRPC client library implementation written in 100% PLSQL. Allows the Oracle DB to easily turn into a webservice consumer, without the need for java.

Tpl makes it easy to serialize your C data using just a handful of API functions. The data is stored in its native binary form for maximum efficiency. C, Perl and XML supported. Data is portable across CPU types and OS's from Unix to Mac to Windows.

AJAX WebService component provides easy and efficient way to explore/invoke any WebServices directly from JavaScript (both RPC and Document style), without additional server-side support. Incorporated WebService Explorer shows many abilities of component

Af-Arch is an Open Source N-tier framework to build distribuited applications. Its license schema allows Open Source and commercial (closed source) applications. This is the foundation to build an new set of applications in a fast and reliable way.

Ajax.NET is an implementation of the AJAX technology used by Google, Orkut, Flickr, ... for the .NET environment. Call server side methods as if they were on the clientside.

Maintain all anaksibolga project components

Apache Thrift is a software framework for scalable cross-language services development. Apache Thrift allows you to define data types and service interfaces in a simple definition file. Taking that file as input, the compiler generates code to be used to easily build RPC clients and servers that communicate seamlessly across programming languages. Thrift is a lightweight, language-independent software stack for point-to-point RPC implementation. Thrift provides clean abstractions and implementations for data transport, data serialization, and application level processing. Thrift is specifically designed to support non-atomic version changes across client and server code. This allows you to upgrade your server while still being able to service older clients; or have newer clients issue requests to older servers. For more details on Thrift's design and implementation, see the Thrift whitepaper included in this distribution, or at the README.md file.