Do not have users accessing Solr directly.
Have your own secure web frontend/ own APIs for it. In this way you can
control secure access.
Secure Solr with https and Kerberos. Have for your web frontend only access
rights needed and for your admins only the access rights they need. Automate
de
Take a look at the ROME API. They have support for Atom 0.3, 1.0, and
just about every RSS format on the planet. It's a very solid API and
widely used in the open source community. There was something on their
mailing list about support for the publishing part of Atom not too
long ago. I think the
What would an update request look like? How close/far is this from the
existing format/functions? Is it just a syntax change from what we have
or would it require something more?
Is this something that can be handled with XSLT processing an atom file?
http://issues.apache.org/jira/browse/SOLR
On 7/3/07, Walter Underwood <[EMAIL PROTECTED]> wrote:
The Atom Publishing Protocol would be a good choice for a rest API to
Solr.
That comes with a spec, interop testing, and an active community.
+1
The Atom Publishing Protocol would be a good choice for a rest API to Solr.
That comes with a spec, interop testing, and an active community.
wunder
On 7/2/07 6:22 PM, "Ian Holsman" <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I've been playing with Kettle (http://kettle.pentaho.org/ ) as a method
> to
