Apache::Request Under Win32?
Excuse me if this is a ridiculous question, but is there any way to install Apache::Request on a Windows box without VC++? This is the output from 'perl Makefile.PL' for libapreq: Warning: Guessing NAME [c] from current directory name. Usage: xsubpp [-v] [-C++] [-except] [-prototypes] [-noversioncheck] [-nolinenumb ers] [-nooptimize] [-noinout] [-noargtypes] [-s pattern] [-typemap typemap]... f ile.xs Writing Makefile for c Writing Makefile for Apache::Request Writing Makefile for Apache::Cookie Writing Makefile for libapreq When I do an 'nmake install' it gives me a couple of lines like: Too many parameters - And then seems to go on without a problem, but I try to 'use Apache::Request();' and it can't find it in @INC. Does anybody have explicit instructions or prequisites for installing this? Thanks in advance. Ryan Adams PS - I'm not actually trying to use Windows for production mod_perl, but I want to be able to develop mod_perl stuff for the production linux box from my laptop when I'm out of the office... -- Ryan Adams [EMAIL PROTECTED] Vitessi Motorsports, Inc. www.vitessi.com Voice: 740/362-9254 Fax: 740/362-0354 -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CyberCash and mod_perl Experiences
Thanks for the info and code. That is essentially what I was doing as well. I was just getting a lot of errors. Looking further into their code, they're misspelling a lot of their own variable names and have some incorrect regex syntax. Lots of "Use of uninitialized value in concatenation...", "Use of unitialized value in substitution..." filling up my httpd error log. It may be that I'm doing some thing wrong, so I'll start from scratch and see where I can get. Some of my frustration has to do with their goofy installation locations. They want me to put the .pm's under a cgi-bin directory, which I don't have since all my dynamic pages run from ContentHandlers. I guess what I really wanted was a library that installed like most other Perl Modules, that didn't require outside binaries and other such things. They're only making an http request to their own server with a message that has been encrypted using DES3. It just seems like that could be done in a much easier way than they seem to be doing it. For example, they use Socket to do the connection, when it seems like LWP would encapsulate it very well. Same thing with the external encryption binaries and the Crypt modules. And yet, I paid their setup fee, so I feel like I've paid for their software to work the way I wanted and rewriting it is effort I shouldn't have to make. I feel like I'm dealing with Microsoft. Thanks everyone for listening to me rant. I'll keep you posted on what I come up with. I'm toying with the idea of writing an CyberCash module for the Business::OnlinePayment interface. Anyone have any idea where to start? RYAN
IPC::open2 under mod_perl
I mentioned my issues with CyberCash yesterday, and I've been trying to work some of the bugs out of the implementation. But I seem to be having problems with their using IPC::open2. Basically, they use separate binaries to encrypt data and decrypt data that is to be sent to their server. The chunk of encrypted data is then sent over a basic, unencrypted http request. They're essentially doing this: IPC::Open2::open2(\*CIPHER, \*PLAINTEXT, '/foo/bar/encryption_binary') or die print PLAINTEXT "A Bunch Of Text To Be Encoded"; close(PLAINTEXT); my $EncryptedData = CIPHER; SomethingWithEncryptedData($EncryptedData); close(CIPHER); And they do the reverse when they get a response. Sometimes it works, but most of the time, it warns that $EncryptedData is uninitialized and CyberCash pukes. I'm assuming that something weird is going on and the open2 is failing. Is this something that can reasonably be done under mod_perl? Any workarounds? Also, in the documentation for IPC it mentions that it won't return failure, but throws an exception. It doesn't look like CyberCash took this into account. What is the best way to fix it and catch the error? (I know this is more Perl than mod_perl...) Ideas are very welcome. Details: Apache 1.3.12 Linux 2.2.14-6.1.1smp mod_perl 1.24 mod_ssl 2.6.6-1.3.12 perl 5.6.0 Thanks in advance... RYAN -- Ryan Adams [EMAIL PROTECTED] Vitessi Motorsports, Inc. www.vitessi.com Voice: 740/362-9254 Fax: 740/362-0354 --
More Info Re: IPC::Open2 Problems
The call to open2 seems to work fine for one or two times after I restart the server. Would that imply that the filehandles are not getting closed somehow? I'm explicitly closing them, to no avail. Also, when I check $! after the open2 call, I'm seeing the same error about "Illegal Seek..." every time. I've searched everywhere I could think of, but haven't found any information on what that means. Anybody encounter this before? I've seen references to needing to build Perl with sfio... I'm not sure what that means, and whether it is applicable to my problem. Can someone clue me in? Thanks, RYAN -- Ryan Adams [EMAIL PROTECTED] Vitessi Motorsports, Inc. www.vitessi.com Voice: 740/362-9254 Fax: 740/362-0354 --
CyberCash and mod_perl Experiences
Hello all, I'm trying to integrate CyberCash with a shopping system that we've developed in-house using mod_perl almost exclusively. I haven't been particularly impressed with the way it installs. We're on a Linux machine and it has a very NT-centric design, in my opinion. I have been able to get test scripts to run from the command-line and through basic mod_cgi execution, but I can't get consistent results when executing them via mod_perl ContentHandlers. In looking through their library files, they are doing some IPC::Open2 calls to executables and some other pretty ugly stuff that may or may not be causing the problems. Does anyone have experience doing this? What approach did you take? Any good documentation? I've read all the CyberCash stuff, but it hasn't given me the kind of answers I wanted. Thanks in advance. Ryan
RE: CyberCash and mod_perl Experiences
I was thinking about Phillip's approach, actually, but the technical details in his ACS system are all in Tcl for AOLServer. Also, I'm not really excited about the liability involved in storing the credit card number in my database. I decided to jump in and start hacking the CyberCash perl libraries and they are full of junk. They don't use "use strict" and when I put it in all of them, it blew up. They don't use scoping in any kind of consistent way and seem to have fundamental issues with perl syntax (They used $#Foo to find the size of %Foo - can you do that? I didn't think so, and the interpreter didn't seem to either - wanted me to declare @Foo...) On a completely unrelated note, my picture is actually in "PA's Guide to Web Publishing". I'm in the section about the dating game. I'm the model they used (not the girl... ;) the guy in the suit. Thanks for the input, RYAN -Original Message- From: Yann Ramin [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 01, 2000 6:06 PM To: Ryan Adams Cc: [EMAIL PROTECTED] Subject: Re: CyberCash and mod_perl Experiences I haven't dealt with CyerCash before, but have some ideas which I read from a somewhat useful book I got for free (Phillip and Alex's Guide to Web Publishing). CyberCash is not reliable. Perfectly valid credit cards fail auth at times, and the service has a tendancy to crap out. What the book suggested to do was to have a backend which goes and queries new orders every x minutes and tries to auth them. They are attempted three times, and after that rejected (and credit card numbers yanked from your DB, replaced with a CyberCash reference). That way what the user sees is a perfectly working system, not knowing that things are dead behind that. My $0.01 Yann On Sun, 01 Oct 2000, you (Ryan Adams) might of written: Hello all, I'm trying to integrate CyberCash with a shopping system that we've developed in-house using mod_perl almost exclusively. I haven't been particularly impressed with the way it installs. We're on a Linux machine and it has a very NT-centric design, in my opinion. I have been able to get test scripts to run from the command-line and through basic mod_cgi execution, but I can't get consistent results when executing them via mod_perl ContentHandlers. In looking through their library files, they are doing some IPC::Open2 calls to executables and some other pretty ugly stuff that may or may not be causing the problems. Does anyone have experience doing this? What approach did you take? Any good documentation? I've read all the CyberCash stuff, but it hasn't given me the kind of answers I wanted. Thanks in advance. Ryan -- Yann Ramin [EMAIL PROTECTED] Atrus Trivalie Productions www.redshift.com/~yramin Monterey High ITwww.montereyhigh.com AIM oddatrus Marina, CA IRM Developer Network Toaster Developer SNTS Developer KLevel Developer