I have worked with Viola-Jones before - it is extremely robust to lighting conditions. However what it is not robust to is angular changes (twisting of face sideways). It is possible that HP are using some kind of naiive algorithm to achieve face tracking, an easy one for e.g. is simple edge analysis for eye recognition (easier if you have a infrared emitter - to exploit the red eye effect) and then using this extrapolate facial dimensions then to facilitate tracking. It is possible they use Viola-Jones for the initial stage to locate the face region and then begin tracking, so even though the VJ tracker is very good, the processing further in the chain isn't so robust. Part of the reason for doing this might be that the VJ tracker is expensive in terms of compute cycles.

The only problem with X forwarding is, if the xserver dies, i.e. your netbook, then the whole workspace dies, the other option is to use some form of xproxy like nx.

This reminded me of an anarchy cookbook/manual I was reading at one time. One of the methods was biological warfare, where you would start off with a brew of relatively harmless bacteria and then start introducing anti-disinfectants to weed out the bacteria that were the strongest and then grow those - one would repeat this process until they were confident enough that when another person (possibly an enemy) when exposed would become either severely ill or die as a result.

over 9000 cpus!!!!!! in all seriousness, this get used so many times, especially by people who use scripting languages (e.g. python/perl/php/ruby/javapoo/next fad) ... who cares if the run time runs like sticky poo down the toilet, just throw more hardware at it.

This could actually work rather well and would require far less infrastructure to do it.

fork rtfa, thats for forkers. mysql is fail ... surprised it has survived this long, its basically sqlite with a server.

no doubt it'd make a good movie then =) ... (like john malkovich)

you can do it put your back into it!

you obviously haven't RTFA or the main purpose of its release

FORTH FTW!

"The dynamic scaling to plan can also be automated" massive retardation here.

its all done in userspace, by the application, sequencing is taken care of usually by attaching header data, and synchronization is taken care using either batched positive acknowledgments, beacon like acknowledgments or negative acknowledgments. Relatively simple, but can lead to terrible inefficiencies ... not to mention a danger to the tubes.

UDP-based protocols tend to operate in userspace, unless this proposed protocol is bringing out a kernel module which I doubt it is. While UDP is good for lossy data like voice or video, it is a terrible idea to put all of the logic of maintaining packet order / data consistency inside userspace - because you have you to cross the kernel space into the userspace, instead of the lower level waking you up saying 'hey I have a packet for you, it is in the correct order and its been verified' - you will have to deal with 'hey I have a packet for you, I have no idea where this packet fits into the data stream and whether this is a packet that I have already given to you, but here it is anyway', it might be terribly more in-efficient than TCP based torrent transfers. Saying this, there may be some good in UDP, swarms can use true multicast (which is impossible with stream oriented protocols) to save overall bandwidth.

this browser may be the one to feed trolls with engrishisms: "all your javascript is crash"

robot actor you say? Steven Seagal has it covered! http://forums.cdcovers.cc/showthread.php?t=163274