bjarlestam

Devise – Taking care of your users

bjarlestam — Wed, 23 Mar 2011 22:02:00 +0000

After working with ruby and rails for the last couple of months I must say it is a true pleasure to work with. So when we hosted the local Ruby User Group (SHRUG) at the Valtech office I thought I should contribute with a lightningtalk. The presentation I did was about Devise a really nice authentication solution for Rails applications that fixes all the basic stuff you need to have users logging in to your site. It was mostly live coding, which may not have been such a good idea ater all. Hope some of you found it amusing at least. Anyway here are the slides:

Context in live events in jQuery 1.4

bjarlestam — Sun, 10 Jan 2010 20:28:55 +0000

Performance tests continued

In my previous post I measured how the performance of a web application is impacted by jQuery live events. The conclusion was that live events will normally not have a big performance impact, but in complex applications with lots of events it can be a problem. An important factor that I didn’t cover very well is the level of nesting in the dom-tree. I have created a test case that demonstrates better how the performance impact changes with a more nested dom-tree.





  
    jQuery 1.4a2 nested live tester
  

  
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...

In this test we have a dom-tree with 30 nested div’s and we register 100 live events. We then trigger a click event on different levels of the tree and measure the time required to process it. On my macbook I get the following result:

click at level 1: 24ms

click at level 5: 54ms

click at level 10: 91ms

click at level 15: 130ms

click at level 20: 174ms

click at level 25: 210ms

click at level 30: 253ms

We see that the performance impact of the live events is greater on clicks that are made deep down a nested dom-tree.

Can the context help?

In my previous post on performance in jquery live events I proposed that it would be a good improvement to support a scope for the live events, so that the performance impact can be limited to a specific part in the dom-tree. One way to implement this could be through the context parameter in the core jQuery() object constructor. When live events were introduced they did not support the use of a context parameter, but the coming jQuery 1.4 release is supposed to support it. More details about this can be found at learningjquery.com. I was curious to se how this context was being used and if it would allow me to limit the impact of the live events to a specific part of dom-tree. To investigate this I modified the above test so that a context is provided when registering the live events. Note that in the previous test as well as this one i use the latest jQuery 1.4 alpha 2 release.





  
    jQuery 1.4a2 nested live tester with context
  

  
    current level...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...

In this test we use one of the nested divs as context. I was hoping that jQuery takes advantage of this context so that we don’t get any performance impact on events triggered above the context element, only events on elements inside the context should get the performance impact. However when I run the tests I get the following result:

context set at level 20

click at level 1: 30ms

click at level 5: 66ms

click at level 10: 113ms

click at level 15: 160ms

click at level 20: 207ms

click at level 25: 255ms

click at level 30: 305ms

We see that the resulting figures are similar to the results where no context was used. The live events even has slightly bigger performance impact now. Events on all elements in the dom-tree gets the performance impact regardless of which context we specify. So the context did not help us here. This is probably due to that jQuery attaches the delegating event on the document instead of the context element. We can verify that jQuery puts the events on the document element with a simple check in firebug. By opening firebug, reloading the test, and then invoking the following command in the console

 jQuery(document).data('events').live

We see that the live events are stored on the document and not on the context element. In my view it would be bad if this behavior is kept in the final release of jQuery 1.4 unless the context is still unsupported like in 1.3. Once the functionality is released it can not be changed without breaking some applications that rely on the current behavior. I guess the idea could be that live events should be kept even if you remove the context element and that you should be able to load the context element dynamically. But I think that it would be more valuable to be able to limit the performance impact by putting the delegating event on the context. It would also provide an easy way to control the lifetime of live events by simply removing the context element.

Performance of jQuery Live events

bjarlestam — Mon, 30 Nov 2009 20:00:25 +0000

Live events is a new feature in jQuery 1.3. It could be used as an alternative to traditional event delegation techniques. It provides a convenient way to implement event delegation. The following code will bind an event handler to the document. When events bubble up jQuery will check if any ancestor of the original target has the class myButton and delegate the event accordingly.

jQuery('.myButtton').live('click', function(){ //do stuff });

This is very convenient when your markup is loaded through ajax or created on the fly by JavaScript. The jQuery documentation provides some more info on how it works.

Performance

Anytime the user clicks anywhere on the document an event will be triggered and jQuery needs to determine if it should delegate it or not.

jQuery will of course need some cpu time to do this check which could potentially result in sluggish behaviour when the user clicks on the page.

Testcases

To help me understand what performance tradeoff I make when using live events, I have set up a few test cases.


"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">


    jQuery live tester


    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    waiting for results...
    Button

Test results

test	Firefox 3.5	IE8	IE7	Chrome	Safari 4
without live events	0.3	1.6	0.5	0.2	0.3
with 10 live events	4.9	9.4	15.6	2.1	3.4
with 100 live events	45	93.8	143.8	21.5	20.5
with 200 live events	94.2	201.6	306.2	36.6	40.6
with 200 live events and large dom	92.2	201.6	306.2	36.9	41.7
with 100 live events with id selector	50.4	90.6	157.8	17.2	19.7
with 100 live events with complex selector	109.1	231.3	373.4	46.9	48.4

The tests were performed using jQuery v1.3.2 on a Pentium4 2.8GHz with 2GB RAM running win xp

Explanation of tests

Basically the tests are done by registering a number of live events and one normal event. We measure the time it takes to process the normal event to see how it gets impacted by the live events. First we measured the time it takes to handle the normal event without any live events registered. This is just to have something to compare against. The result is just a fraction of a millisecond. Next we add 10 live events to see how this impacts the performance. The event now takes 4.9 milliseconds to process in FireFox 3.5. To push it a bit we add more live events. We then see that 100 live events results in ca 45 milliseconds and 200 live events results in ca 94.2 milliseconds. It seem like the performance impact is approximately linear when adding more live events. What about dom size? In the first tests the markup is very simple with a very small dom-tree. A bigger dom-tree might have some impact on the performance. To test this we simply add 500 div’s to the dom and test again. This is what test no 5 does. Surprisingly we see that the performance impact of the live events does not get worse when the dom size increases. What about different types of selectors? One might also suspect that the performance is depending on the type of selector used. In test 3 a simple class selector was used. Test 6 instead uses an id selector and test 7 uses a more complext selector. We see that there is no big performance difference between a simple id selector and a simple class selector. However when using more complex selector the performance impact seems to be worse.

Conclusion

The tests show that adding live events will have some performance impact. As long as the number of registered live events is small the impact is not significant. However if you have a complex site with many events you may run into trouble, especially if you need to support browsers with poor JavaScript performance.

What could be done to improve this?

In my view it would have been better if jQuery would let you somehow define what element you want to register the delegating event on, so that the impact is limited to a specific context. The default could still be to add it to the document. This could be done in at least two different ways. One option could be to add the delegating event to the context given in the core jQuery(expression, context) function. I dont know enough about the internals of jQuery to say how feasible this is.

Another option could be to redefine the live method as follows:

jQuery('').live( '', eventType, eventHandler);

so the current live behaviour would be achieved by

jQuery('document').live('


Update:
After a comment from Jonathan Sharp I added some more tests to see how a more nested dom-tree affects the performance. When adding 30 nested divs we can see that a click deep down the tee will be affected more by the live events.
var button = jQuery('button').appendTo('body');
button.bind('click', function() {});
addEvents(100, '.garbage');
//Add nested DOM-tree
var element = jQuery('body');
for(var i=0; i<30; i++) {
    element = jQuery('').appendTo(element);
}

measureClick(jQuery('#result1'), 'click outside of nested elements: ');
button.appendTo(element);
measureClick(jQuery('#result2'), 'click inside of nested elements: ');
In this test I add 30 nested divs to the dom-tree and I add 100 live events. In firefox the output of this test is:
click outside of nested elements: 27.2

click inside of nested elements: 251.9
This shows that when I click on an element that is a direct child of the body, the performance is ok, but when I click an element deep down the nested divs the performance impact is much worse.
This makes it even more desirable to be able to define the context when registering a live event.
Update 2 – jQuery 1.4a1
On request I have run the same tests as above on the same machine but with the new alpha release of jQuery 1.4. The results are as follows:



test
Firefox 3.5
IE8
Chrome
Safari 4


without live events
0.3
1.6
0.2
0.3


with 10 live events
4.5
9.4
2.1
2.7


with 100 live events
38.5
79.8
19.6
19.9


with 200 live events
73.9
162.7
40.8
39.6


with 200 live events and large dom
79.5
167.3
42.2
39.9


with 100 live events with id selector
37.7
90.7
18.9
20.1


with 100 live events with complex selector
91.2
172
31.8
45.7



The test are not very precise. Running the tests twice will not produce the exact same results. It is clear though that the performance has been improved slightly.

test	Firefox 3.5	IE8	Chrome	Safari 4
without live events	0.3	1.6	0.2	0.3
with 10 live events	4.5	9.4	2.1	2.7
with 100 live events	38.5	79.8	19.6	19.9
with 200 live events	73.9	162.7	40.8	39.6
with 200 live events and large dom	79.5	167.3	42.2	39.9
with 100 live events with id selector	37.7	90.7	18.9	20.1
with 100 live events with complex selector	91.2	172	31.8	45.7



RESTful Web Services the easy way with JAX-RS
bjarlestam — Tue, 15 Sep 2009 06:36:33 +0000
Here are the slides that I have prepared for my talk at JavaForum this evening. It took me some time to cut it down to 34 slides and then still many of them had to become extra spare slides. I had to realize that 30 minutes is really not much time. On the other hand I’ve seen many 10 minute lightning talks where the speaker manages to deliver the essence of a pretty complicated topic, so I shouldn’t really complain.


         


REST presentation
bjarlestam — Tue, 16 Jun 2009 12:45:27 +0000
I have put together some slides about the basic principles in REST. The real presentation is actually implemented as a JAX-RS application. I started out with a django version, but I needed a Java-angle on it so I had to switch to JAX-RS.


         


Some reflections from Agile Sweden 2009
bjarlestam — Wed, 10 Jun 2009 08:30:21 +0000
It’s been two days of interesting talks and discussions at Agila Sverige 2009. These are some of my reflections from the event:
Bring back the simplicity
There was a lot of talk about bringing back simplicity as one of the cornerstones in agile development. XP was all about communication, simplicity, feedback and courage. Somehow the principle of using the simplest solution has been lost when we standardize on agile methods. Many of the talks were about simplicity, for example Johan talked about “Standards vs. Cargo cult“, Niklas talked about “Simplicity as means, opportunity as goal” and Marcus asked “Where did the simplest working solution go?”. All very good presentations. A somewhat related presentation was about allowing variation to facilitate evolution (variation + selection = evolution). The advice was to bring in some variation in each project and select the working solutions. When I think of it, that is usually how I work as well.
Kanban and Scrum
Another hot topic was Scrum and Kanban. Kanban is of course the new and trendy thing to talk about. Henrik gave a good talk where he managed to describe the similarities and differences in just 10 minutes. There were also some good presentations about how to apply Kanban and how Kanban and Scrum can be combined.
Is Scrum the new RUP?
I don’t remember who it was, but someone asked the question whether Scrum is the new RUP. The Agile movement was a reaction on stiff processes being forced down from upper management, but today we see the same thing happening with Scrum. Anna Herting for example described that to solve their problem with prioritizing maintenance activities they used Kanban, but still had to call it Scrum to satisfy the managers. In my view it is always bad to just apply a process methodology without thinking about what the needs are. You also want to continuously improve on the process and extend it with new ways of working. What you need is some principles to follow that will take you in the right direction and simple tools to choose from and use as inspiration.
People, Teams and how we behave
Many of the talks were about how to behave as responsible developers and how to create good team cultures. For example Åke made a talk about self-learning and asking good questions, asking them at the right time and asking lagom many questions. We also got the good advice from Jocke to promise behavior instead of results. He explained that promises are tools to gain trust, synchronize with people and create motivation. Chris talked about the different stages of learning. How you go from unconsciously incompetent -> consciously incompetent -> consciously competent -> unconsciously competent. The unconsciously incompetent needs inspiration while the unconsciously competent needs reflection. Lots of talk about creating openness and trust in teams, for example by establishing common team values.
All in all I had a great time. I really enjoyed the open and interactive format with Lightning Talks and Open Space sessions.

         


A wave of new HTML5 stuff from Google
bjarlestam — Mon, 01 Jun 2009 14:17:12 +0000
Google is pushing rather hard for HTML5 now with Google Wave, the new flash free HTML 5 version of YouTube  and more HTML5 support in Chrome . It’s nice that someone is pushing for open standards instead of proprietary stuff (read Silverlight, Flex, JavaFX).

         


Simple JavaScript AOP framework
bjarlestam — Wed, 27 May 2009 14:32:54 +0000
Here’s a simple JavaScript AOP framework for aspect oriented programming that I have been playing with:
/**
 * AOP framework for aspect oriented programming in JavaScript
 */

 var AOP = AOP || function() {

     //Private methods

     function toArray(iterable) {
         if (!iterable) return [];
         if (iterable.toArray) return iterable.toArray();
         var length = iterable.length || 0, results = new Array(length);
         while (length--) results[length] = iterable[length];
         return results;
     }

     //Public methods

     var public = {
         around: function(obj, fname, advice) {
             var oldFunc = obj[fname];
             obj[fname] = function() {
                 var args = [oldFunc].concat(toArray(arguments));
                 return advice.apply(this, args);
             };
         },

         before: function(obj, fname, advice) {
             var oldFunc = obj[fname];
             obj[fname] = function() {
                 var args = [oldFunc].concat(toArray(arguments));
                 advice.apply(this, args);
                 return oldFunc.apply(this, arguments);
             };
         },

         after: function(obj, fname, advice) {
             var oldFunc = obj[fname];
             obj[fname] = function() {
                 var args = [oldFunc].concat(toArray(arguments));
                 oldFunc.apply(this, arguments);
                 return advice.apply(this, args);
             };
         },

         callMethod: function(args) {
             var argsArray = toArray(args);
             return argsArray[0].apply(this, argsArray.slice(1));
         }
     };

     return public;
 }();
You can try it out with the following test code:
function logBeforeAndAfter() {
	console.log("before");
	AOP.callMethod(arguments);
	console.log("after");
}

function logAfter(f) {
	console.log("after ...");
	if(arguments[1] == "world") {
		console.log("its world");
	}
}

testObject = {
	hello: function(who) {
		console.log("hello " + who);
	}
}

AOP.around(testObject, "hello", logBeforeAndAfter);

//	AOP.before(testObject, "hello", function() {console.log("before");})

//	AOP.after(testObject, "hello", logAfter);

testObject.hello("world");
Maybe not so useful yet, but a nice exercise anyway.

         


Learn JavaScript and learn it properly
bjarlestam — Wed, 25 Feb 2009 23:56:10 +0000
JavaScript is the global web version of the unix shell script, simply increadibly useful. With tools like ubiquity and greasemonkey you can do lots of cool stuff. Also all the nice frameworks, GUI components and the JSON APIs makes it a very useful language.
So to help you learn JavaScript and for my own reference I have listed some really good resources
The JavaScript Programming Language

http://video.yahoo.com/watch/111593/1710507

http://video.yahoo.com/watch/111594/1710553

http://video.yahoo.com/watch/111595/1710607

http://video.yahoo.com/watch/111596/1710658
Advanced JavaScript

http://video.yahoo.com/watch/111585/1027823

http://video.yahoo.com/watch/111586/1027832

http://video.yahoo.com/watch/111587/1027854
JavaScript – The Good Parts

http://video.yahoo.com/watch/630959/2974197
Interactive tutorial by John Resig:

http://ejohn.org/apps/learn/
JavaScript best practices

http://www.slideshare.net/cheilmann/javascript-best-practices-1041724
Blogs:

http://www.robertnyman.com/

http://www.wait-till-i.com/

http://remysharp.com/

http://frontendbook.com/

http://mattsnider.com/

http://ejohn.org/

         


Shouldn’t the web be location aware by now?
bjarlestam — Sun, 04 Jan 2009 22:21:02 +0000
More and more devices come with built in GPS and mobile browsing has become more popular with the iPhone and all the ultra mobile laptops such as the Asus EEEPC. So, mow it seems to be the right time to start building websites that adapt themselves to your current location.
To make the web applications location aware we need to get the location from somewhere. The most obvious way would be that the web browser makes it available by retrieving it from a GPS, mobile cell information, WiFi access point etc. It can provide the information to the web applications through a JavaScript API.
What is available?
Unfortunately there is no standard that is supported by all the major browsers yet, but there are some really interesting things ongoing.
For Firefox you have the Geode plugin that provides access to location information via a JavaScript API. The location information in Geode is based on Skyhook which calculates it from nearby WiFi access points. Skyhook has a database with MAC addresses of access points, mostly in USA and Canada.
The Firefox 3.1 beta release includes out of the box support for a JavaScript API. Firefox 3.1 will allow the user to choose a geolocation service provider, which can either be a peripheral device like a GPS, or a web-based service provider. The API is based on the W3C draft described below.
Google has done quite some work to location enable the web. As announced in their code blog they provide an AJAX API that lets you get a rough location based on the ip-address. Google Gears also supports a location API very similar to the W3C draft and with Google as editor in W3C I think the chance of conformance is rather good. Google Gears can use GPS, mobile cell id or WiFi access point to determine the location. As you probably know Gears is available as a plugin for Safari, Firefox and IE and of course comes built in to Chrome. Also Windows Mobile 5 and 6 devices are supported and of course it comes pre-installed on Anrdoid phones.
The IPhone does currently not provide any JavaScript API for location information and it does not support Google Gears. There is however an application available for Jailbroken IPhones that implements the W3C draft API described below.
The W3C Geolocation JavaScript API draft


Google has submitted a simplified version of their Google Gears API to W3C. This draft specification is currently worked on in the Geolocation Working Group in W3C. The working group plans to have an official recommendation ready by end of 2009.
The current draft version of this API includes a method for getting location information and another to get periodic updates of location information.

Example of a “one-shot” position request.
    // Callback function
    function showMap(position) {
      // Show a map centered at
      // (position.coords.latitude, position.coords.longitude).
    }

    // One-shot position request.
    navigator.geolocation.getCurrentPosition(showMap);


Example of requesting repeated position updates.
    // Callback function
    function scrollMap(position) {
      // Scroll the map so that it is centered at
      // (position.coords.latitude, position.coords.longitude).
    }

    // Request repeated updates.
    var watchId = navigator.geolocation.watchPosition(scrollMap);

    function buttonClickHandler() {
      // Cancel the updates when the user clicks a button.
      navigator.geolocation.clearWatch(watchId);
    }