"scott.stark(a)jboss.org" wrote :
| I'm not opposed to this driving features, like a new keystore format to allow for these types of certs, as you know I love the idea of smart cards replacing the password hell that exists today.
|
Not sufficient. It is still single factor. There is a real need for two or multi-factor authentication.
SRP (Scott's Robust Password) system also does not make the cut. ;)
Any legal issues (patents, licensing) with bouncy castle api?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980201#3980201
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980201
This doesn't make any sense to me.
NIO and streams don't work well together.
NIO is based around a fixed size buffers - this is a quite different way of working to the old stream based io that most people are used to.
As I said earlier in this thread I would be suprised if you can create an API that works equally well for blocking and NIO.
If we want to get the best performance the API must expose access to the underlying buffers. There's no way around this without sacrificing performance which is not an option IMHO.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980195#3980195
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980195
The only observation I have from the document is about byte arrays
(http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingRemotingAPIExtensions)
If we need to deal with byte[] directly, having byte[] on the signature will force us (and remoting) to duplicate the object, maybe serialize it before flushing it out to the streaming.
I would like to propose something like access to Input/OutputStream directly saving the need of converting an object to byte[] before sending it.
RemotingOutputStream stream = client.getDirectOutputStream();
| stream.close(); // will dismiss the stream and but client in a state to receive other calls.
|
|
So, the example would be:
Client client = new Client("bidirectional://jmsserverbox:7777", "EXAMPLE-SUBSYSTEM");
client.connect()
client.addHandler(new MessagingCallbackHandler());
Object result = client.invoke(new MessagingInvocation());
OutputStream output = client.getDirectOutput(); // this will return a RemotingOutputStream
InputStream input = client.getDirectInput();
out.write(...);
input.read(); // reads the answer
out.close();
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980188#3980188
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980188