tag:blogger.com,1999:blog-151343742024-03-13T23:38:15.108+01:00Google and what's newWhat do you think one can bring to the web nobody has before ?Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-15134374.post-49304734943300962112009-10-16T22:00:00.000+02:002009-10-16T22:00:48.072+02:00Pushing Erlang with xmlrpcTo help contribute to the Erlang community I've published my <a href="http://rds13.github.com/xmlrpc/">hacks</a> over <a href="http://www.erlang.org/user.html#xmlrpc-1.13">xmlrpc Erlang</a> library.<br />
<br />
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.Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-6330655119096437422009-10-10T12:06:00.000+02:002009-10-10T12:06:29.387+02:00AppEngine next language ?Python, Java, ...<br />
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. <br />
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.Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-59221540691859482522009-09-18T20:51:00.003+02:002009-09-18T21:04:59.410+02:00Mind the limits !Running load simulator programs from linux might lead you to a limit ! This limit is often met through messages like :<br /><pre>Too many opened files</pre><br />or in Erlang a more criptic message for the newbie :<br /><pre>{{badmatch,{<b class="highlight">error</b>,<b class="highlight">emfile</b>}},[{gen_tcp....</pre><br /><br />It means you've bump on the hard limit of opened files by processes.<br />Changing the values in /etc/limits.conf or /etc/security/limits.conf will allow you to raise those limits.<br />Don't forget to close <span style="font-weight: bold;">all</span> your shell sessions to allow the system to effectively raise the limit !Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-67503739190349936762009-05-02T16:31:00.004+02:002009-05-02T16:38:47.153+02:00OOPHM mode with GWT on OSXSuffice to say that <a href="http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM">UsingOOPHM</a> and building GWT from source allows to launch this mode<br />via<br /><pre>ant oophm</pre>The behaviour of the interface is a little bit rough on the edges though on OSX.Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-22153241232903220042009-05-02T13:53:00.004+02:002009-05-02T16:30:49.128+02:00Building GWT from SVN on OSXBuilding GWT from svn trunk is documented in <a href="http://code.google.com/intl/fr/webtoolkit/makinggwtbetter.html#compiling">Making GWT Better</a>.<br />But the compile process invoke a nasty parsing of svn info command which fails if your langage setting is not english.<br />You'll find that in build-tools/ant-gwt/src/com/google/gwt/ant/taskdefs/SvnInfo.java :<br /><br /><pre><br />/**<br />* A pattern that matches the Repository Root line in svn info output.<br />*/<br />private static final Pattern ROOT_PATTERN =<br /> Pattern.compile("\\s*Repository Root:\\s*(" + URL_REGEX + ")\\s*");<br /></pre><br />This pattern fails miserably on svn info like this :<br /><pre>Chemin : .<br />URL : http://google-web-toolkit.googlecode.com/svn/trunk<br />Racine du dépôt : http://google-web-toolkit.googlecode.com/svn<br />UUID du dépôt : 8db76d5a-ed1c-0410-87a9-c151d255dfc7<br />Révision : 5320<br />Type de noeud : répertoire<br />Tâche programmée : normale<br />Auteur de la dernière modification : jgw@google.com<br />Révision de la dernière modification : 5320<br />Date de la dernière modification: 2009-05-01 22:23:02 +0200 (Ven, 01 mai 2009)<br /></pre><br />I had to switch form iTerm to Terminal to achieve a good setup of my environment to achieve a sucessful building.<br />In Terminal preferences uncheck the LANG setting flag and in your shell do<br /><pre><br />export LANG=en_US<br />ant<br /></pre><br /><br />This should be enough to build GWT successfully !<br /><br />PS: Pay attention to not interfere with JDK 1.6 if you have it installed on your machine.Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-1126621347926460812005-09-13T16:22:00.000+02:002005-09-13T16:28:16.460+02:00Ajax librariesJean-Marc Orliaguet jmo at ita.chalmers.se on Z3lab mailing-list Thu Jul 14 21:26:20 CEST 2005<br /><br />Hi!<br /><br />I've been testing various "Ajax" libraries recently and these are my<br />impressions (they correspond to the use cases that I have, others<br />certainly have other needs):<br /><br />- first of all there is a lot of buzz around Ajax, when you start<br />looking for an Ajax framework you are likely to find all sorts of<br />libraries that do just anything on earth: drag-and-drop, visual<br />effects, animations, sortable lists; they belong to the "Application<br />framework" category.<br />Then there are the XMLHttpRequest wrapper libraries (belonging to the so<br />called "Infrastructure framework" category).<br /><br />- some of the libraries are meant to be kept simple and lightweight,<br />others are really heavy-weight libraries. The Rico [1] / Prototype [2]<br />libs for instance take a lot of CPU on every page load (up to 3 or 4<br />seconds depending on your hardware). You really feel it when you tune<br />down your CPU to 800MHz. Obviously you are not supposed to reload the page.<br /><br />- for drag-and-drop stuff, contextual menus, etc. I find that PDLib [7]<br />is just fine for what I need. It has the advantage compared to the other<br />libraries that I've seen so far to refer to classes of elements as<br />opposed to a collection of element Ids. The Rico lib [2] and<br />script.aculo.us [3] for instance need to register as many Ids as there<br />draggable and droppable elements. With PDLib, you just have to declare a<br />CSS class as draggable and a class as droppable. That makes a difference<br />when you have lots of elements on a page. The only problem with the<br />PDLib library is that there are a lots of versions around. I have done<br />some local modifications on it for CPSSkins [8] with bug fixes from<br />CompositePack [9], etc.<br /><br />- By the way: what does drag-and-drop have to do with AJAX?<br />drag-and-drop has been around for years... My impression is that it is<br />better to keep the XMLHttpRequest part separate from the fancy stuff.<br /><br />- So the next question is: what is the core functionality you'd expect<br />from an "Ajax" JS library? I've done a list of use cases for cpsskins<br />and it all comes down to one thing: being able to send requests to the<br />server and getting the result of the request inserted into the page in a<br />given place without reloading the page.<br /><br />- An important factor is that it should go fast, so I started to look to<br />'lightweight' libraries [5] [6] with the minimum number of features<br />implemented. Sarissa [4] has a lot of XML/XSLT features that I feel<br />could as well be implemented in zope and that I presently have little<br />need for.<br /><br />So I tested 'DataRequestor.js' [5] which is exactly what I need (simple<br />to use and fast).<br /><br />- I've set up a test / demo page that updates a fragment of a page with<br />the date fetched from zope every time the uses clicks on the button:<br />http://cvs.ita.chalmers.se:8980/ajax/demo<br /><br />- Conclusion: be careful with the buzz that surrounds Ajax, identify the<br />needs of your application, do benchmarks.<br /><br />I hope that this review can be useful.<br />regards<br />/JM<br /><br />References:<br />-----------------<br />[1] http://openrico.org/demos.page - rico.js (69kB ...) + prototype.js<br />(28kB)<br />[2] http://prototype.conio.net/ - prototype.js (28kB)<br />[3] http://script.aculo.us/ - dragdrop.js (19kB) - effects.js (21kB) +<br />prototype.js (28kB)<br /><br />[4] http://sarissa.sourceforge.net/doc/ - sarissa.js (27kB)<br />[5] http://mikewest.org/projects.php?action=viewProject&projectID=1 -<br />DataRequestor.js (16kB / documentation included - 6.4kB without the doc)<br />[6] http://xkr.us/code/javascript/XHConn/ XHConn.js (1.4kB)<br /><br />[7] http://svn.zope.org/pdlib/trunk/<br />[8]<br />http://svn.nuxeo.org/trac/pub/file/CPSSkins/trunk/skins/CPSSkins/cpsskins_pdlib.js.dtml<br />[9] http://plone.org/products/compositepackRomhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0tag:blogger.com,1999:blog-15134374.post-1123232769098409812005-08-05T11:03:00.000+02:002005-08-05T11:06:46.556+02:00The amazing webWho can image what the web will look like in two years ?<br />If you look back in time on what the web look like in 2002-2003...<br />Where Google was ?Romhttp://www.blogger.com/profile/01144649251240780944noreply@blogger.com0