Re: Communicating with a PHP script (and pretending I'm a browser)

Date	2014-11-11 09:55 -0800
From	Ethan Furman <ethan@stoneleaf.us>
Subject	Re: Communicating with a PHP script (and pretending I'm a browser)
References	<CACwCsY46yYFQwdYdriTSYSvLYF=xs6L2zanN9gofkWkoHvj_fA@mail.gmail.com> <CAPTjJmpR_Yj-rwTHsodDquHuML3vX2vQrjCiseJcV5e+nfZGZg@mail.gmail.com> <CACwCsY5denavfJQYS6x0Lknj-WJW2qfskVdYcuOuJ4P8h0u6gQ@mail.gmail.com> <CAPM-O+z9wdFcO7Hj=oKh-M1Cht-Wt35UWxavEPPbGxNGHOxpqA@mail.gmail.com> <CACwCsY6copVYtNe-az7jd2vzcgF76FPnn9t-Q0u6NGevY8Y-Bg@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.15682.1415728535.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 11/11/2014 09:30 AM, Larry Martell wrote:
>
> They are technically savvy. They are a 100% PHP shop. They have a big,
> complicated app that they've been working on for 10 years. No one
> there knows python or django. They want to put some new frontends on
> their app. I was bought in for another project (involving Google Tag
> Manager and Google Analytics), which I completed. Then they asked me
> about this project. I told them they should redo their app in Flask or
> Django. It took some cajoling, but they eventually said OK. But then a
> few days later they said before I went off and reimplemented
> everything in python, could I just build the new frontend and call the
> existing PHP code. This would enable them to get the new frontends out
> to their clients sooner, and then I could go back and port the PHP to
> python. I don't see what is so wrong with that.

Sounds like an excellent game plan to me.  :)

--
~Ethan~

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Communicating with a PHP script (and pretending I'm a browser) Ethan Furman <ethan@stoneleaf.us> - 2014-11-11 09:55 -0800

csiph-web