in reply to dbiproxy and compression

Silly question, perhaps, but do you have compression enabled on the DBI::ProxyServer server? I just had a look at the module page on CPAN, and I didn't see a 'compression' argument.

Obviously, both the server and the client have to have compression (the same compression) turned on for this to work.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Replies are listed 'Best First'.
Re^2: dbiproxy and compression
by bcrust (Novice) on Nov 06, 2007 at 17:24 UTC
    Yes, I ran the dbiproxy with --compression. It seems that my problem is on the client side.

    I ran the proxy in the debugger and stepped through the code as it received the connection. It certainly attempted to Compress::Zlib::uncompress on every message received from the socket. The problem was that the message was not compressed.

    However, I can find no mention in the client-side connection libraries that compression was an option. I added compression=gzip to the DSN (as suggested in the O'Reilly book, but not in any PODs) to no effect. Is this just a pipe dream?

    Has anyone successfully ever gotten DBI::Proxy to talk to dbiproxy (DBI::ProxyServer) with compression enabled?

    Alternately, is there another way to transparently compress data with the DBI modules?

    Ben

[reply]
        The problem was that the message was not compressed.

      OK -- so why wasn't the message compressed? Is Compress::Zlib not installed on the client side?

      Am I missing something obvious?

      Alex / talexb / Toronto

      "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

[reply]
        That is the question. Compress::Zlib is installed all around.

        It appears that the client-side DBI/DBD modules are not doing any sort of compression and the compression=gzip option is being ignored in the DSN string.

        The reason I ask if this is at all possible is because I can't find any mention of compression in DBI, DBD::Proxy or any other module that I can think of.

        A removed feature? A good idea that was only partially implemented perhaps?

        I could dicker with the dbiproxy to uncompress only certainly messages (not the connection information) and then run Compress::Zlib::compress to compress the data before I execute, but I was hoping for something more transparent and less hacky.

        Am I missing something obvious? Is this something folks use regularly?

        Ben

[reply]

In Section Seekers of Perl Wisdom