FS-2746 --resolve large xmlrpc update thanks garmt

This commit is contained in:
Jeff Lenk committed 2012-10-13 11:37:25 -05:00
1 parent 37ecad9903
commit 6b6c83a718
397 files changed
+41821 -33840

No files matched your search

+66 -44
View File
@@ -5,18 +5,25 @@
#include <winsock.h> // For XMLRPC_SOCKET (= SOCKET)
#endif
#include "xmlrpc-c/config.h" // For XMLRPC_SOCKET
#include "xmlrpc-c/base.hpp"
#include "abyss.h"
#include <xmlrpc-c/config.h> // For XMLRPC_SOCKET
#include <xmlrpc-c/c_util.h>
#include <xmlrpc-c/base.hpp>
#include <xmlrpc-c/registry.hpp>
#include <xmlrpc-c/abyss.h>
namespace xmlrpc_c {
class serverAbyss {
struct serverAbyss_impl;
class XMLRPC_DLLEXPORT serverAbyss {
public:
class constrOpt {
struct constrOpt_impl;
class XMLRPC_DLLEXPORT constrOpt {
public:
constrOpt();
~constrOpt();
constrOpt & registryPtr (xmlrpc_c::registryPtr const& arg);
constrOpt & registryP (const xmlrpc_c::registry * const& arg);
@@ -29,33 +36,14 @@ public:
constrOpt & dontAdvertise (bool const& arg);
constrOpt & uriPath (std::string const& arg);
constrOpt & chunkResponse (bool const& arg);
constrOpt & allowOrigin (std::string const& arg);
constrOpt & accessCtlMaxAge (unsigned int const& arg);
constrOpt & serverOwnsSignals (bool const& arg);
constrOpt & expectSigchld (bool const& arg);
struct value {
xmlrpc_c::registryPtr registryPtr;
const xmlrpc_c::registry * registryP;
XMLRPC_SOCKET socketFd;
unsigned int portNumber;
std::string logFileName;
unsigned int keepaliveTimeout;
unsigned int keepaliveMaxConn;
unsigned int timeout;
bool dontAdvertise;
std::string uriPath;
bool chunkResponse;
} value;
struct {
bool registryPtr;
bool registryP;
bool socketFd;
bool portNumber;
bool logFileName;
bool keepaliveTimeout;
bool keepaliveMaxConn;
bool timeout;
bool dontAdvertise;
bool uriPath;
bool chunkResponse;
} present;
private:
struct constrOpt_impl * implP;
friend class serverAbyss;
};
serverAbyss(constrOpt const& opt);
@@ -82,10 +70,15 @@ public:
void
runConn(int const socketFd);
#ifndef WIN32
void
sigchld(pid_t pid);
#endif
void
terminate();
class shutdown : public xmlrpc_c::registry::shutdown {
class XMLRPC_DLLEXPORT shutdown : public xmlrpc_c::registry::shutdown {
public:
shutdown(xmlrpc_c::serverAbyss * const severAbyssP);
virtual ~shutdown();
@@ -95,35 +88,64 @@ public:
};
private:
// The user has the choice of supplying the registry by plain pointer
// (and managing the object's existence himself) or by autoObjectPtr
// (with automatic management). 'registryPtr' exists here only to
// maintain a reference count in the case that the user supplied an
// autoObjectPtr. The object doesn't reference the C++ registry
// object except during construction, because the C registry is the
// real registry.
xmlrpc_c::registryPtr registryPtr;
TServer cServer;
void
setAdditionalServerParms(constrOpt const& opt);
serverAbyss_impl * implP;
void
initialize(constrOpt const& opt);
};
class XMLRPC_DLLEXPORT callInfo_serverAbyss : public xmlrpc_c::callInfo {
/*----------------------------------------------------------------------------
This is information about how an XML-RPC call arrived via an Abyss server.
It is available to the user's XML-RPC method execute() method, so for
example an XML-RPC method might execute differently depending upon the
IP address of the client.
This is for a user of a xmlrpc_c::serverAbyss server.
-----------------------------------------------------------------------------*/
public:
callInfo_serverAbyss(xmlrpc_c::serverAbyss * const abyssServerP,
TSession * const abyssSessionP);
xmlrpc_c::serverAbyss * const serverAbyssP;
// The server that is processing the RPC.
TSession * const abyssSessionP;
// The HTTP transaction that embodies the RPC. You can ask this
// object things like what the IP address of the client is.
};
class XMLRPC_DLLEXPORT callInfo_abyss : public xmlrpc_c::callInfo {
/*----------------------------------------------------------------------------
This is information about how an XML-RPC call arrived via an Abyss server.
It is available to the user's XML-RPC method execute() method, so for
example an XML-RPC method might execute differently depending upon the
IP address of the client.
This is for a user with his own Abyss server, using
the "set_handlers" routines to make it into an XML-RPC server.
-----------------------------------------------------------------------------*/
public:
callInfo_abyss(TSession * const abyssSessionP);
TSession * abyssSessionP;
// The HTTP transaction that embodies the RPC. You can ask this
// object things like what the IP address of the client is.
};
XMLRPC_DLLEXPORT
void
server_abyss_set_handlers(TServer * const srvP,
xmlrpc_c::registry const& registry,
std::string const& uriPath = "/RPC2");
XMLRPC_DLLEXPORT
void
server_abyss_set_handlers(TServer * const srvP,
const xmlrpc_c::registry * const registryP,
std::string const& uriPath = "/RPC2");
XMLRPC_DLLEXPORT
void
server_abyss_set_handlers(TServer * const srvP,
xmlrpc_c::registryPtr const registryPtr,