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 On 6/28/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: The following page has been changed by BrianLucas: : http://wiki.apache.org/solr/SolrUpdate So now in addition to the Java Update client sitting in Jira, we have some PHP Update/Query code on the Wiki ... time to start getting serious about how we want to manage the various client libraries people may/will be writting in all the various languages they'll be writting them in. the big issues i wonder about are: * testing ... not just unit testing, but basic syntax checking ... is there a way to automate checks that PHP scripts compile as part of our ant builds? * levels of support ... are there some languages/APIs that we want to consider part of the "core" and ensure work with any server changes, and others that are more "contrib"ish? if so what makes that determination? * varient implimetnations ... what if differnet people write/contribute multiple client APIs for the same language .. do we want to pick one to be the "official" API for that language? -Hoss
