[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Build broken with new AIO tests
by clebert.suconic@jboss.com
"timfox" wrote : Ok, I worked out what is happening:
|
| AIO is picked up successfully when running tests on the command line, but is not picked up when running tests in eclipse.
|
| Probably because java.lib path is not set.
|
|
That's what I said few posts ago:
"clebert.suconic(a)jboss.com" wrote : I have changed the native library load a bit to make sure the conditional test for 32 and 64 bits are working.
|
| To make your life easier during development, you could change the script that starts your IDE to something like this:
|
| export LD_LIBRARY_PATH=/extra/work-clebert/workspaces/jboss-messaging-trunk/trunk/native/bin:$LD_LIBRARY_PATH
| | /usr/share/eclipse/eclipse
| |
|
|
"timfox" wrote :
|
| Can we avoid this dependency on java lib path? I don't really like the idea of users having to set env properties to get our software to run. It's messy IMHO.
The only way around would be to install the library on /usr/lib, and we should have that when we have the RPM or .DEB package.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149440#4149440
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149440
17 years, 11 months
[Design of Messaging on JBoss (Messaging/JBoss)] - To UTF-8 or not to UTF-8 that is the question
by timfox
JBM 1.4 uses UTF-8 encoding for all strings sent in messages, e.g. properties, text message bodies etc.
This provides a good compression if using higher unicode characters a lot (e.g. chinese), however the java UTF-8 encoding is *really slow*.
For JBM 2.0 we're currently the SimpleString class I wrote (which doesn't copy itself on the drop of a hat like String) and we marshall it as a simple sequence of bytes.
In my tests this is about 40 times faster than UTF-8 encoding the same string. :)
Problem is SimpleString currently only stores each character as two bytes, which is fine for the vast majority of unicode characters but won't encode the far reaches of unicode which require 4 bytes.
I can change SImpleString to use 4 bytes per character but this is going to make the marshalled form big - especially in the case of standard latin characters or european - about 4 times the size as encoded!
How do you think we should deal with this?
One possibility is we write our own UTF-like encoding implementation...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149433#4149433
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149433
17 years, 11 months