Perl to PHP API Conversion
Project ID: 1319663965
Project Details
  • Status:
    Closed (Chosen Programmer: petrican; Rated 10 out of 10)
  • Posted:
    10/26/2011 at 17:19 EST
  • Closed:
    11/2/2011 at 1:31 EST
  • Project Creator:
    Rated 10 out of 10 for this project.
  • Budget:
    N/A
  • Description:
    Hi

    I want to hire a new programmer to help create the ScriptLance API that will be used by other developers to interact with our backend.

    We've started work on a Perl version. Only basic public actions (view projects, users, reviews, portfolios, etc) with output in XML and JSON. Now we would rather build the rest of the API in PHP.

    I need someone to convert to PHP the approx 1500 lines of Perl code we already have (Perl code available upon request in PMB). I want good, efficient, well commented, organized coding. Your code will be used as a base for all future API code, so it must be good.

    Please bid for this PHP conversion, but also provide us with your hourly rate for additional PHP coding work on the API, including authorization and integration with OAuth (already installed on server). If this project goes well we will hire you to create more API scripts and consult on the API design.

    We want someone familiar with APIs. Please tell us about other API work you have done.

    Thank you
    -Rene Trescases
    Owner, ScriptLance.com
    Additional Info (Added 10/28/2011 at 16:36 EST)...
    There are several suggestions in this article that we would like to adopt in our API: http://blog.programmableweb.com/2010/03/31/7-ways-to-make-your-api-more-successful/

    Including:
    -partial response handling
    -Customizable Output Markup
    -caching (maybe. need to discuss.)
    -multiple output formats. XML and JSON will be used, but api must be designed so it's easy to add more in future.

    Also, we expect:
    -secure code. SQL injection-proof.
    -descriptive input parameter ids (e.g. SL_ProjectID vs pid).
    -standard variable ids. Meaning: don't use "name" for a person's name in one place, and then "name" again somewhere else for a project name.
    -ability to do public and private access. private sections will require a registered api key and authentication via oauth.
    -documenting the code you create, so we know what data to send to api and what result to expect.
    -don't convert our perl code exactly line by line. we expect better code, incl good use of PHP's different features.


    That is what I mean by efficient code. It may not all apply to this first project, but its worth noting, so you know what will be expected later. Thanks.
  • Tags:
Project Bids



(4 bids have been placed. r3n3inc has chosen to keep all bids for this project hidden.)