LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2014

CODE4LIB February 2014

Subject:

Re: PHP HTTP Client preference

From:

Karen Coombs <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 13 Feb 2014 11:43:24 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (156 lines)

Hi everyone,

Wanted to let people here know that the OCLC WSKey or OCLC Auth
library in PHP which the community helped contribute feedback about is
now available via GitHub
(https://github.com/OCLC-Developer-Network/oclc-auth-php). You can
learn more about what it does via our announcement on the Developer
Network blog - http://t.co/vaNDsvw01w. Please send any questions or
comments via emails to devnet[at]oclc[dot]org

Karen

On Fri, Sep 13, 2013 at 10:54 AM, Karen Coombs <[log in to unmask]> wrote:
> Thanks everyone for your helpful feedback on the PHP HTTP Client
> library. I ended up choosing Guzzle and am in the process of
> incorporating and testing it. If you're interested in my rationale and
> when the OCLC WSKey (Web Service key) code library will be available,
> check out my post on the development effort on the Developer Network
> website - http://oc.lc/RyoUKC
>
> Karen
>
> On Tue, Sep 3, 2013 at 6:01 PM, Walker, David <[log in to unmask]> wrote:
>> We're also using Guzzle, and really like it.
>>
>> --Dave
>>
>> -------------------------
>> David Walker
>> Director, Systemwide Digital Library Services
>> California State University
>> 562-355-4845
>>
>>
>> -----Original Message-----
>> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Karen Coombs
>> Sent: Tuesday, September 03, 2013 3:52 PM
>> To: [log in to unmask]
>> Subject: Re: [CODE4LIB] PHP HTTP Client preference
>>
>> Thanks so much for all the feedback guys. Keep it coming. I'll definitely check out Guzzle as an option.
>>
>> Karen
>>
>> On Tue, Sep 3, 2013 at 4:26 PM, Hagedon, Mike <[log in to unmask]> wrote:
>>> Guzzle++
>>>
>>> -----Original Message-----
>>> From: Code for Libraries [mailto:[log in to unmask]] On Behalf
>>> Of Kevin S. Clarke
>>> Sent: Tuesday, September 03, 2013 8:37 AM
>>> To: [log in to unmask]
>>> Subject: Re: [CODE4LIB] PHP HTTP Client preference
>>>
>>> Another +1 for Guzzle
>>>
>>> Kevin
>>>
>>>
>>>
>>> On Tue, Sep 3, 2013 at 11:32 AM, Kevin Reiss <[log in to unmask]> wrote:
>>>
>>>> I can second Guzzle. We have been using it for our our in-house PHP
>>>> applications that require HTTP interactions for about six months and
>>>> it has worked out very well. Guzzle has also been incorporated as the
>>>> new default HTTP client in the next version of Drupal.
>>>>
>>>>
>>>> ________________________________
>>>>  From: Ross Singer <[log in to unmask]>
>>>> To: [log in to unmask]
>>>> Sent: Tuesday, September 3, 2013 10:59 AM
>>>> Subject: Re: [CODE4LIB] PHP HTTP Client preference
>>>>
>>>>
>>>> Hey Karen,
>>>>
>>>> We use Guzzle: http://guzzlephp.org/
>>>>
>>>> It's nice, seems to work well for our needs, is available in
>>>> packagist, and is the HTTP client library in the official AWS SDK
>>>> libraries (which was a big endorsement, in our view).
>>>>
>>>> We're still in the process of moving all of our clients over to it
>>>> (we built a homegrown HTTP client on top of CURL first), but have
>>>> been really impressed with it so far.
>>>>
>>>> -Ross.
>>>>
>>>> On Sep 3, 2013, at 10:49 AM, "Coombs,Karen" <[log in to unmask]> wrote:
>>>>
>>>> > One project I'm working on for OCLC right now is building a set of
>>>> object-oriented client libraries in PHP that will assist developers
>>>> with interacting with our web services. The first of these libraries
>>>> we'd like to release provides classes for authentication and
>>>> authorization to our web services. You can read more about
>>>> Authentication/Authorization and our web services on the Developer
>>>> Network site<http://oc.lc/devnet>
>>>> >
>>>> > The purpose of this project is to make a simple and easy to use
>>>> > object
>>>> oriented library that supports our various authentication methods.
>>>> >
>>>> > This library need to make HTTP requests and I've looked at a number
>>>> > of
>>>> potential libraries and HTTP clients in PHP.
>>>> >
>>>> > Why am I not just considering using CURL natively?
>>>> >
>>>> > The standard CURL functions in PHP are not object-oriented. All of
>>>> > our
>>>> code libraries (both our authentication/authorization library and
>>>> future libraries for interacting with the REST services themselves)
>>>> need to perform a robust set of HTTP interactions. Using the standard
>>>> CURL functions would very likely increase the size of the code
>>>> libraries and the potential for errors and inconsistencies within the
>>>> code base because of how much we use HTTP.
>>>> >
>>>> > Given this, I believe there are three possible options and would
>>>> > like to
>>>> get the community's feedback on which option you would prefer.
>>>> >
>>>> > Option 1. - Write my own HTTP Client on top of the standard PHP
>>>> > CURL
>>>> implementation. This means people using the code library can only
>>>> download it and now worry about any dependencies. However, that means
>>>> adding extra code to our library which, although essential, isn't at
>>>> the core of what we're trying to support. My fear is that my client
>>>> will never be as good as an existing client.
>>>> >
>>>> > Option 2. - Use HTTPful code library (http://phphttpclient.com/).
>>>> > This
>>>> is a well developed and supported code base which is designed
>>>> specifically to support REST interactions. It is easy to install via
>>>> Composer or Phar, or manually. It is slim and trim and only does the HTTP Client functions.
>>>> It does create a dependency on an external (but small) library.
>>>> >
>>>> > Option 3. - Use the Zend 2 HTTPClient. This is a well developed and
>>>> supported code base. The biggest downside is that Zend is a massive
>>>> code library to require. A developer could choose to download only
>>>> the specific set of classes that we are dependent on, but asking
>>>> people to do this may prove confusing to some developers.
>>>> >
>>>> > I'd appreciate your feedback so we can provide the most useful set
>>>> > of
>>>> libraries to the community.
>>>> >
>>>> > Karen
>>>> >
>>>> > Karen A. Coombs
>>>> > Senior Product Analyst
>>>> > WorldShare Platform
>>>> > [log in to unmask]<mailto:[log in to unmask]>
>>>> > 614-764-4068
>>>> > Skype: librarywebchic
>>>>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager