Dan,
I think getting the Solr PHP client into PEAR is a worthwhile effort.
And we welcome your contribution towards achieving this goal.
Bill
On 3/2/07, Dan Scott <[EMAIL PROTECTED]> wrote:
On 02/03/07, Bill Au <[EMAIL PROTECTED]> wrote:
> Now that we have an "official" place for Solr client. I think we should
put
> the PHP
> update and query clients there.
>
> I haven't found anything in ant that will compile PHP scripts. But if
we
> assume PHP
> is install on the local system, we can also do an <exec>.
>
> We have to start somewhere. Once there is a client, then we can improve
it
> and/or add additional API to it. I think it should be driven by the
user
> community.
>
> Bill
For PHP, I think it would be best to maintain the official Solr client
as part of the PEAR repository -- probably in a package named
"Services_Solr". PHP folk are used to downloading pure PHP libraries
through the "pear install XXX" command.
Of course, that would mean rewriting the PHP client to be compliant
with PEAR standards, including being written for PHP 5 with no
E_STRICT warnings, error-handling through exceptions, having unit
tests, and having documentation. The benefit of these requirements is
that it results in interoperability with other PEAR libraries.
If the contributor of the current Solr PHP client isn't interested in
going through the PEAR process for proposing and contributing a
package, and meeting all of the PEAR repository standards, I'll
volunteer to write a new client from scratch. After Erik's tutorial at
code4lib this week, I feel that I grok Solr sufficiently -- and I have
a fair bit of experience with the PEAR process.
Dan Scott
