On 3/9/11 12:26 PM, Max Rydahl Andersen wrote:
>>> Are you planning to use just the HTTP API or would you be
using the Native / Remoting API?
>>
>> HTTP
>
> For HTTP the complete set being considered is 'BASIC, Digest, Certificate i.e.
SSL and Kerberos/SPNEGO' - what are you using for your connections to the server?
There is quite a bit of client side support for all these mechanisms in Java already.
>
>
http://download.oracle.com/javase/6/docs/technotes/guides/net/http-auth.html
okey - so we should be "safe" as long as we can find a good way to have the
user provide the credentials.
>> Haven't seen any good usecases for using the native/remote api yet.
>
> I don't think the HTTP side will be too difficult to support but using Remoting
will also automatically give you all of the supported mechanisms for the Native
connections.
More automatically than using the http auth api ?
The difference between native and http is that with native you get a
java API that does all of the protocol stuff for you. With the HTTP API,
you will have to do generate and parse JSON. For the web console we also
allow for encoded DMR messages over HTTP, although if you are using DMR,
thats about 80% of the java API.
--
Jason T. Greene
JBoss, a division of Red Hat