To help contribute to the Erlang community I've published my hacks over xmlrpc Erlang library.
This library has already received various patches that you can found around the web. I've decided to rather build a repository in the hope that it might drains contributions and help keep this library alive.
October 16, 2009
October 10, 2009
AppEngine next language ?
Python, Java, ...
Java also opened the door for JRuby. The next language could be a less generic one. The upcoming Wave service powered over XMPP and suggesting OpenFire server for support could well be the application killer boosting Erlang language via a server like ejabberd.
Erlang is opensource, powered by a virtual machine, highly suitable for network oriented applications. Surely the community around the language is sparse but it's gaining more and more interest as people face threading problems.
Java also opened the door for JRuby. The next language could be a less generic one. The upcoming Wave service powered over XMPP and suggesting OpenFire server for support could well be the application killer boosting Erlang language via a server like ejabberd.
Erlang is opensource, powered by a virtual machine, highly suitable for network oriented applications. Surely the community around the language is sparse but it's gaining more and more interest as people face threading problems.
September 18, 2009
Mind the limits !
Running load simulator programs from linux might lead you to a limit ! This limit is often met through messages like :
or in Erlang a more criptic message for the newbie :
It means you've bump on the hard limit of opened files by processes.
Changing the values in /etc/limits.conf or /etc/security/limits.conf will allow you to raise those limits.
Don't forget to close all your shell sessions to allow the system to effectively raise the limit !
Too many opened files
or in Erlang a more criptic message for the newbie :
{{badmatch,{error,emfile}},[{gen_tcp....
It means you've bump on the hard limit of opened files by processes.
Changing the values in /etc/limits.conf or /etc/security/limits.conf will allow you to raise those limits.
Don't forget to close all your shell sessions to allow the system to effectively raise the limit !
May 2, 2009
OOPHM mode with GWT on OSX
Suffice to say that UsingOOPHM and building GWT from source allows to launch this mode
via
via
ant oophmThe behaviour of the interface is a little bit rough on the edges though on OSX.
Building GWT from SVN on OSX
Building GWT from svn trunk is documented in Making GWT Better.
But the compile process invoke a nasty parsing of svn info command which fails if your langage setting is not english.
You'll find that in build-tools/ant-gwt/src/com/google/gwt/ant/taskdefs/SvnInfo.java :
This pattern fails miserably on svn info like this :
I had to switch form iTerm to Terminal to achieve a good setup of my environment to achieve a sucessful building.
In Terminal preferences uncheck the LANG setting flag and in your shell do
This should be enough to build GWT successfully !
PS: Pay attention to not interfere with JDK 1.6 if you have it installed on your machine.
But the compile process invoke a nasty parsing of svn info command which fails if your langage setting is not english.
You'll find that in build-tools/ant-gwt/src/com/google/gwt/ant/taskdefs/SvnInfo.java :
/**
* A pattern that matches the Repository Root line in svn info output.
*/
private static final Pattern ROOT_PATTERN =
Pattern.compile("\\s*Repository Root:\\s*(" + URL_REGEX + ")\\s*");
This pattern fails miserably on svn info like this :
Chemin : .
URL : http://google-web-toolkit.googlecode.com/svn/trunk
Racine du dépôt : http://google-web-toolkit.googlecode.com/svn
UUID du dépôt : 8db76d5a-ed1c-0410-87a9-c151d255dfc7
Révision : 5320
Type de noeud : répertoire
Tâche programmée : normale
Auteur de la dernière modification : jgw@google.com
Révision de la dernière modification : 5320
Date de la dernière modification: 2009-05-01 22:23:02 +0200 (Ven, 01 mai 2009)
I had to switch form iTerm to Terminal to achieve a good setup of my environment to achieve a sucessful building.
In Terminal preferences uncheck the LANG setting flag and in your shell do
export LANG=en_US
ant
This should be enough to build GWT successfully !
PS: Pay attention to not interfere with JDK 1.6 if you have it installed on your machine.
Subscribe to:
Posts (Atom)