Erland Nylend wrote:
The CPE is the client, sending HTTP POST
_queries_ with some data. The remote management server (apache server)
is sending HTTP POST _replies_ back, but those also contains data.
Okay, that makes sense. Persistent connections shouldn't require any
additional work on your
One more thing. Did you know that there are SOAP-Modules available:
- http://search.cpan.org/~rkobes/Apache2-SOAP-0.72/
- http://search.cpan.org/~byrne/SOAP-Lite-0.69/
Tom
Erland Nylend wrote:
>Thanks for replying,
>
>On 2006-08-25, 13:04, Perrin Harkins wrote:
>
>
>>HTTP has defined roles of
Hi,
Don't parse data your own!
Use:
- CGI.pm (comes with your perl installation by default) or
- libapreq http://search.cpan.org/~joesuf/libapreq2-2.08/
I'd say libapreq is the better choice if you start from scratch. The
documentation you are referring
to talks about internal redirect's which y
Thanks for replying,
On 2006-08-25, 13:04, Perrin Harkins wrote:
> HTTP has defined roles of client and server. You can't make HTTP
> requests and respond to other HTTP requests on a single socket
> connection, at least not without writing your own protocol which will
> not really be HTTP.
I may
On Fri, 2006-08-25 at 18:56 +0200, Erland Nylend wrote:
> In short, a router sends a http POST to the webserver, expects a
> HTTP POST reply back, sends a new HTTP POST .. and so on, all on the
> same connection. This way soap-envelopes are transmitted between the
> peers.
HTTP has defined roles o
Hello,
I'm new to modperl, and I have a question regarding how to handle
multiple POST-requests in one single connection.
For those interested, I need to communicate with CPE routers using
tr069 (http://dslforum.org)
In short, a router sends a http POST to the webserver, expects a
HTTP POST repl
