Return-Path: X-Original-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DA9D0D183 for ; Wed, 3 Oct 2012 09:58:38 +0000 (UTC) Received: (qmail 74422 invoked by uid 500); 3 Oct 2012 09:58:38 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 73971 invoked by uid 500); 3 Oct 2012 09:58:31 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 73917 invoked by uid 99); 3 Oct 2012 09:58:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 09:58:29 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of evgeny@skyfence.com designates 216.32.180.16 as permitted sender) Received: from [216.32.180.16] (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.16) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 09:58:19 +0000 Received: from mail89-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE008.bigfish.com (10.7.40.28) with Microsoft SMTP Server id 14.1.225.23; Wed, 3 Oct 2012 09:57:58 +0000 Received: from mail89-va3 (localhost [127.0.0.1]) by mail89-va3-R.bigfish.com (Postfix) with ESMTP id 09D37C0155 for ; Wed, 3 Oct 2012 09:57:58 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.253.197;KIP:(null);UIP:(null);IPV:NLI;H:DBXPRD0710HT004.eurprd07.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(zzc85fh4015Izz1202h1d1ah1d2ahzz17326ah8275bh8275dhz2fh2a8h668h839hd25hf0ah107ah1288h12a5h12bdh137ah1441h1155h) Received-SPF: pass (mail89-va3: domain of skyfence.com designates 157.56.253.197 as permitted sender) client-ip=157.56.253.197; envelope-from=evgeny@skyfence.com; helo=DBXPRD0710HT004.eurprd07.prod.outlook.com ;.outlook.com ; Received: from mail89-va3 (localhost.localdomain [127.0.0.1]) by mail89-va3 (MessageSwitch) id 1349258275266921_14672; Wed, 3 Oct 2012 09:57:55 +0000 (UTC) Received: from VA3EHSMHS027.bigfish.com (unknown [10.7.14.238]) by mail89-va3.bigfish.com (Postfix) with ESMTP id 3BE891A0056 for ; Wed, 3 Oct 2012 09:57:55 +0000 (UTC) Received: from DBXPRD0710HT004.eurprd07.prod.outlook.com (157.56.253.197) by VA3EHSMHS027.bigfish.com (10.7.99.37) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 3 Oct 2012 09:57:54 +0000 Received: from DBXPRD0710MB372.eurprd07.prod.outlook.com ([169.254.8.209]) by DBXPRD0710HT004.eurprd07.prod.outlook.com ([10.255.79.167]) with mapi id 14.16.0207.009; Wed, 3 Oct 2012 09:57:51 +0000 From: Evgeny Shvidky To: "modules-dev@httpd.apache.org" Subject: RPC over HTTP Thread-Topic: RPC over HTTP Thread-Index: Ac2hS1pH8NBA6CgWSBS7Ytfh9dWY6w== Date: Wed, 3 Oct 2012 09:57:50 +0000 Message-ID: <7F1BDE99A6D2D3428162AF33F59630E8101137DE@DBXPRD0710MB372.eurprd07.prod.outlook.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [62.219.139.99] Content-Type: multipart/alternative; boundary="_000_7F1BDE99A6D2D3428162AF33F59630E8101137DEDBXPRD0710MB372_" MIME-Version: 1.0 X-OriginatorOrg: skyfence.com --_000_7F1BDE99A6D2D3428162AF33F59630E8101137DEDBXPRD0710MB372_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am developing a new module on C. One of the requirements of my module is to receive and handle RPC over HTTP= protocol. RPC over HTTP opens two HTTP/1.1 requests: One with request method RPC_IN_DATA to send data to the server, and second = one with method RPC_OUT_DATA to send data back to the client. The body cons= ists of raw binary data, and the connections are apparently re-used for sev= eral RPCs. Here's an example of an IN connection header: RPC_IN_DATA /rpc/rpcproxy.dll?:6002 HTTP/1.1 Content-Length: 1073741824 ... After connections are established client sends on "IN" channel RPC message = with 104 bytes. I use the following apache API's in order to read these client message. ap_setup_client_block(userReq, REQUEST_CHUNKED_ERROR); ap_should_client_block(userReq) ap_get_client_block(userReq, buf, size) The problem is "ap_should_client_block" function returns "1" (means there i= s message to read) but "ap_get_client_block" returns error (-1) and nothing= read. How should I read client's data? Is there any other API for it? Thanks, Evgeny --_000_7F1BDE99A6D2D3428162AF33F59630E8101137DEDBXPRD0710MB372_--