Planet Apache

Bryan Pendleton: Google have open-sourced their JavaScript library

2009-11-07T00:42:16+00:00

Another powerful and sophisticated open source JavaScript library has joined the party.

Among the things that seem interesting about Google Closure are:

Their approach is to introduce an explicit compilation step, so that developers can feel confident in writing well-commented maintainable source, which is then compiled by the Closure compiler down to a smaller and tighter deployable JavaScript program

They've gone with a templating approach. Templating approaches seem to come and go, dating back to things like ASP and JSP last century, and probably older systems before that -- I think ColdFusion was a templating system.

Their infrastructure runs both server-side and client-side, and supports Java as the implementation language on the server-side (and of course JavaScript as the language on the client side.

Since this library is from Google, you can be sure that it is thorough, powerful, and sophisticated, and therefore worthy of study.

I guess that means I've got something else to learn about now!

Davanum Srinivas: Better RSS feed for IBM WebSphere Application Server forum

2009-11-06T23:21:59+00:00

The websphere forum (see below) feeds are truncated http://www.ibm.com/developerworks/forums/forum.jspa?forumID=266&start=0 You need to add “&Full=true” to get all the content as shown below: http://www.ibm.com/developerworks/forums/rss/rssmessages.jspa?forumID=266&Full=true

Matt Raible: User Interface Schema Definitions

2009-11-06T22:22:46+00:00

On my current project, we're developing a "designer" tool that allows users to build forms in their browser. These forms are displayed in various channels (e.g. web, mobile, sms) to capture data and make decisions based on user input.

When I joined the project, it was in a proof-of-concept phase and the form definitions created where serialized as XML (using JAXB) with element names that seemed logical. Now that we're moving the PoC to production mode, we're thinking it might be better to change our form definitions to leverage something that's more "industry standard". If nothing else, it'll help with marketing. ;-)

This week, I was tasked with doing research on "existing user interface schema definitions". I'm writing this post to see if there's any major specifications I'm missing. I plan on providing my recommendation to my team on Monday. Here's what I've found so far:

User Interface Markup Language (UIML): At 120 pages, the 4.0 spec seems very detailed. I'm not sure we'd use all of it, but it's interesting how the spec allows you to describe the initial tree structure (<structure>) and to dynamically modify its structure (<restructure>). It also has the notion of templates, which mirrors a similar concept we have in our application. Furthermore, it has VoiceXML support, which could be useful if we use call centers as a channel.
USer Interface eXtensible Markup Language (UsiXML): I admit that I haven't read much of this specification -- mostly because the UIML spec seemed to cover most of what we needed (especially since we're most interested in describing forms). As far as a I can tell, the major difference between UsiXML is its being being submitted to the W3C for standardization (according to Wikipedia), while UIML is being standardized by OASIS. Beyond that, I find it strange that UIML's spec is 120 pages and UsiXML is 121. Neither project seems to have any activity this year.
Numerous others: including AAIML, AUIML, XIML, XUL, XAML and XForms. XForms seems like it may be the most logical if we're only interested in form layout and describing elements within them.

If all we're interested in is an XSD to define our forms, the most appealing specs have them: UIML, UsiXML and XForms. If activity is any sort of motivator for adoption, it's interesting to note that XForms 1.1 was submitted as a W3C recommendation a couple weeks ago (October 20, 2009).

If you've developed some sort of "form designer" tool that renders to multiple channels, I'd love to hear about your experience. Did you use some sort of industry standard to define your form elements, layout, etc. or did you come up with your own?

Luciano Resende: ApacheCon 2009 Session: Applying OSGi after the fact

2009-11-06T22:03:57+00:00

ApacheCon US 2009 is almost finished, and I'm done with my last Apache Tuscany/OSGi session.

Tuscany: Applying OSGi modularity after the fact
Fri, 06 November 2009 11:15 by Luciano Resende

Slides are now available

Ben Laurie: SSL MitM Attack, Part 2

2009-11-06T11:46:18+00:00

A lot can happen in a day. Yesterday the news broke that SSL was compromised. We immediately (OK, it took about 10 hours) released a new version of OpenSSL, 0.9.8l, which mitigates the problem by completely disabling renegotiation. Obviously this will break some sites, and so is not a full fix, so the next step is to implement Eric Rescorla’s TLS extension. However, before I get on with that, it seems I have a few questions to answer.

Firstly, I must thank the anonymous poster who said “OpenSSL is written by monkeys”. But dude, you should’ve included the link. I’ve been meaning to link to that for ages. Well, days.

Secondly, as Marsh said, there is a better answer for people who need renegotiation. This is the extension mentioned above. It won’t work unless clients also implement that, but we are working on that, too (and clearly any client that uses OpenSSL will get it for free as soon as I get the next version out).

To the bloke who asked about ISA and OWA: I have no idea what either of those are.

Does this affect SGC (Server-Gated Cryptography)? I don’t actually know. I think it does, because I think SGC uses renegotiation, but I am not sure. If anyone knows, comment!

To the “but this is just XSRF” (Cross-site request forgery) guy:

XSRF does not give the attacker control over headers.
Your attack didn’t work on me: I didn’t click the link.
HTTP is not the only protocol that uses SSL.

Though the fact that this attack doesn’t actually make HTTP much worse is a pretty damning indictment of HTTP (and HTML)!

Will this patch break session resumption? No – and nor will the 0.9.8l release, which does the same thing more elaborately and correctly.

Finally, even once we’ve implement the extension it seems to me this is not really the true fix – really applications should be aware of renegotiations and not carry trust across their boundaries. But more on that later, I’ve got code to write.

Claus Ibsen: How buggy is your integration stack?

2009-11-06T08:22:18+00:00

This morning I had another blog topic planned but as usually I start by a cup of coffee and check the news, mails and tweets.

I thought Dan Kulp's blog post, How buggy is your SOAP stack was really good. It inspired me to check upon the situation with Apache Camel. I recommend reading his blog entry first before reading mine.

I will keep the investigations on Camel solely as people can do their own investigation on other integration projects.

As of this morning, november the 5th 2009 these are the numbers from Apache Camel JIRA:

2139 tickets in total
159 outstanding tickets (7% of total)

And looking at the 159 outstanding we have:

147 improvements, new features, etc. (all except bugs)
12 bugs

So in total we have reported at total of 12 bugs in Camel out of 159 outstanding issues. That is yet again around 7-8% of the outstanding tickets which is a bug.

Lets go over those 12 bugs and check what they cover

CAMEL-1769: It boils down to the Camel web console when it shows the routes rendered in Groovy it has trouble rendering complex expressions. This is not a bug which affects runtime as the groovy render is used to view the routes.

CAMEL-1788: Flatpack does not work with OSGi. Really not a Camel bug. The flatpack library is rather old and not OSGi ready. Loading its resource file on the classpath does not work well in OSGi land. The reported have reported this to the Flatpack issue tracker. We could in fact close this as its not a problem in Camel.

CAMEL-1974: Charles Moulliards excellent OSGi tutorial had some cosmetic typos and it could benefit to upgrade to latest Karaf standard. He is currently working on this.

CAMEL-1893: The camel-cxf code appears to under a rare situation to set the HTTP status code twice using different case. William Tam have been assigned this ticket.

CAMEL-1898: Hadrian is looking into the build process having a problem with generating the pdf manual during this process. It can however be generated manually thereafter.

CAMEL-1913: camel-jetty and multipart data. This is kinda an improvement.

CAMEL-1941: The tracer does not trace doTry .. doCatch .. doFinally correctly. This only affects diagnostics trace logging. Routing your messages using doTry ... et all works fine.

CAMEL-2001: Relates to the transactedInOut option on the camel-jms component. Its a bit confusing what its useable for. We are discussing this on the mailinglist whether to remove this option. And/or improve the wiki documentation about it.

CAMEL-2021: Guillaume Nodet is working on improving OSGi in Camel. Currently there is an issue with mixed versions running in Karaf.

CAMEL-2059: Relates to its not too easy to do custom error handling with transacted routes. I will look into this when I start writing the transaction chapter in my book. Which is in fact the next chapter I will write.

CAMEL-2129: camel-cxf has an misleading exception message when a call times out. Willem Jiang and Christian Schneider have already fixed this. Code is committed. So this ticket will be closed when Willem does this later today.

CAMEL-2137: Reported yesterday. Related to using Camel in ServiceMix 3.x with JBI.

Notice that the bugs listed here are all fairly new. CAMEL-1769 is created on june 28th 2009.

As of today there has been 698 bugs reported to Camel and of which only 12 is open, that is less than 2% open of all reported bugs.

We have rigorous many unit tests in Camel 2.x at this time we have > 4000 unit tests. That also helps keeps the bug count low.

Then we have a couple of discussions going on the mailinglist which may be a bug in Camel. Lets go over the ones I can remember working with recently.

1) Camel Mail issue with unsupported charset by dcheckoway

This is an end user who consumes mail from a mail server which contains a mail that is using a weird charset which is not supported in the JDK itself. We are working with him to add a feature that tries to change the mail message to remove that charset to see if we can then have the SUN Mail API process the mail.

2) JMS Transactions and RequestReply - transactedInOut=true not working? by jonathanq

See CAMEL-2001 above

3) Problem of skipped items/stories in Camel RSS reader by Cliff Court

An end user is using camel-rss to read some feeds and it appears to skip some feeds. We wonder what the issue is whether its the ROME framework that does the actual RSS work.

4) Error handling with recipientList by mcrive

This is an end user using Camel 2.0.0 who wants to do custom error handling and have precisely information which endpoint failed in case of an error. This feature is already implemented out of the box in 2.1. But the end user wants to use 2.0.0. Have advised him a solution that could work in 2.0 which by adding unit tests also proves. However on his end there is still an issue when its the FTP endpoint that fails. Unit tests in Camel itself shows that it works.

There may be a couple of more issues ongoing on the mailinglist. But the end users haven't reported back etc.

I think the state in Camel is excellent.

I end this blog by answering the blog title:

How buggy is your integration stack? Camel its not buggy.

Matt Raible: Consulting, SOFEA, Grails and GWT at next week's Denver JUG

2009-11-06T06:00:15+00:00

Next Wednesday, I'll be at Denver's JUG meeting to talk about Independent Consulting and Building SOFEA Applications with Grails and GWT. The first talk will be a a panel discussion among local independent consultants, including James Goodwill, Matthew McCullough, Tim Berglund and myself.

This session explores the trials and tribulations of an independent consultant. How do you find contracts? Should you setup an LLC, an S-Corp or just be a sole proprietorship? What about health insurance and benefits? Are recruiters helpful or hurtful? Learn lots of tips and tricks to get your dream job and your ideal lifestyle.

The Grails and GWT talk is a preview of a talk I'll be doing at the Rich Web Experience in December. Below is a rewrite of the abstract in first-person.

Earlier this year, I participated in a major enhancement of a high-traffic well-known internet site. The company wanted us to quickly re-architect their site and use a modern Ajax framework to do it with. An Ajax Framework evaluation was done to help the team choose the best framework for their skillset. The application was built with a SOFEA architecture using GWT on the frontend and Grails/REST on the backend.

This talk will cover how Bryan Noll, Scott Nicholls, James Goodwill and I came to choose GWT and Grails, as well as stumbling blocks we encountered along the way. In addition, we'll explore many topics such as raw GWT vs. GXT/SmartGWT, the Maven GWT Plugin, modularizing your code, multiple EntryPoints, MVP, integration testing and JSON parsing with Overlay Types.

If you're in Denver next Wednesday night (November 11th), you should stop by the Denver JUG meeting. It'll be a fun night and there's sure to be a few beers afterward.

Bryan Pendleton: Ant integration with application servers is too hard

2009-11-06T01:49:19+00:00

I spend way too much of my time at work wrestling with Ant scripts that try to integrate with application servers.

Some application servers do a better job of this than others, but overall the current state of the art in this area is still as described in the Ant manual:

<parallel> <wlrun ... > <sequential> <sleep seconds="30"/> <junit fork="true" forkmode="once" ... > <wlstop/> </sequential> </parallel>
This example represents a typical pattern for testing a server application. In one thread the server is started (the <wlrun> task). The other thread consists of a three tasks which are performed in sequence. The <sleep> task is used to give the server time to come up. Another task which is capable of validating that the server is available could be used in place of the <sleep> task. The <junit> test harness then runs, again in its own JVM. Once the tests are complete, the server is stopped (using <wlstop> in this example), allowing both threads to complete. The <parallel> task will also complete at this time and the build will then continue.

Let's stop for a bit and critique this approach:

First, we have the complexity of the <parallel> and <sequential> tasks, which are complicated and intricate. As the Ant manual itself says,

Anyone trying to run large Ant task sequences in parallel ... is implicitly taking on the task of identifying and fixing all concurrency bugs [in] the tasks that they run. ... Accordingly, while this task has uses, it should be considered an advanced task ...

Secondly, consider the ugly <sleep> call: why did we have to sleep? How long do we need to sleep? What happens if we sleep for too long, or for not long enough? As the Ant manual notes, there are sometimes ways around this, but they require assistance from the application server.

Lastly, what happens when something fails? How do you ensure that, having started the application server, you can reliably shut it down? What happens if you try to shut it down, but it never actually started up? And so forth.

Furthermore, there are many other interactions that one needs to have with an application server beyond just starting and stopping it:

What's the status of this application server? Is it up or down?

Deploy or undeploy an application to the server. Query the current version of a deployed application; re-deploy a different version of an application, either with or without stopping and re-starting the application and/or the server

Find out if the server has encountered any errors; capture the diagnostic error logs from the server.

Adjust the configuration of the server: give it different resources, change its operating parameters, etc.

Install or un-install an application server from scratch.

And many more.

All of these tasks are routine jobs that I'd like to be able to reliably automate, and over the years (decades!!) I have made some progress in doing so.

But still, all those hours spent in trying to write and maintain reliable Ant automation scripts for application server integration.

Is there a better way?

Daniel Kulp: How buggy is your SOAP stack

2009-11-06T00:39:57+00:00

One of the fun things about attending conferences such as ApacheCon is that you get to meet with users of the software I work on and hear “real world” stories of the issues they’ve run into. I talked to one user yesterday that presented a common story that I’ve heard over and over again from many users, but it really got me thinking.

Basically, a short while ago, he was tasked with upgrading some older web services to get them off of Apache Axis. They started porting to Axis2 assuming that would be the easiest effort. After hitting bugs and spending a lot of time trying to work around issues and such, they punted on the effort and switched to CXF. For them, CXF “just worked”.

I hear the same basic thing from many users. CXF just “works”. It does what it says it will do relatively easily (relative term, nothing in WS-* is designed to be easy) and bugs, when found, are usually fixed quickly, but most users I’ve talked to having found any real bugs to log. It just “works”.

For some reason, the person I talked to yesterday got me thinking about the various Open Source SOAP stacks and how “buggy” they are and kind of wondered if that could be quantified. One of the nice things about the open source stacks is the issue trackers are also “open”. Thus, it shouldn’t be too hard. Famous last words.

There are two main issues with trying to compare bug counts:

Features: Each of the three major open source stacks (Axis2, CXF, Metro), while they all implement the same basic specs, they also have unique features. For example, CXF has bugs logged for the CORBA binding, JAX-RS, Distributed OSGi, etc… that the others wouldn’t have. Axis2 has bugs for the UDP transport which is not available in the others. Etc….
Issue tracker layout: Each of the projects handle their issue tracker differently. CXF has a single project in JIRA and all bugs for everything are logged there. Metro has their issues split into two trackers, one for the base JAX-WS implementation and another for the WS-* stuff. Axis2 splits things across a bunch of JIRAs: a core area, one for Rampart, one for Sandesha, one for Kandula, transports, etc….

With that in mind, lets look at some numbers. To make things simple, I looked at the full “bug” count from CXF including all the features including JAX-RS, CORBA, DOSGi, etc…. Thus, the CXF counts are relatively inflated compared to the others. I didn’t look at feature requests, wishes, tasks, etc… Just bugs. For Metro, I looked at the “defects” only for the JAXWS RI and WSIT trackers. For Axis2, to make things simple, I only looked at the “bugs” in the core “Axis2″ jira and didn’t bother looking at the others. I didn’t need to as you’ll see.

As of this morning, Nov 5, 2009, the counts are:

CXF	78
Metro	173 (63 core, 110 WSIT)
Axis2	514

I think those numbers paint a pretty good picture of the state of stacks. However, it’s not the whole picture. Another useful stat is the number of “critical” or “blocker” bugs. (For Metro, P1 or P2 level)

	Blocker	Critical
CXF	0	2
Metro	0	26
Axis2	16	90

Another interesting stat is how many bugs logged in the last year or 6 months remain open. This shows how well the community responds to users bug reports.

	Last Year	6 Months
CXF	50/441 (11%)	36/237 (15%)
Metro	59/335 (18%)	44/222 (20%)
Axis2	189/332 (57%)	96/168 (57%)

Anyway, that last table is quite interesting to me. Any non-trivial software (more than “Hello World”) has bugs. (as anyone that implements WS-* will tell you, WS-* is REALLY non-trivial) When selecting an open source project for use in your enterprise, the questions you need to ask are:

How likely am I to hit a bug?
If I do hit a bug, how serious is it likely to be?
More importantly, if I hit a bug, how likely will a fix be made available in a timely manner?

That last question is critical. As I mentioned, all software has bugs. Getting those bugs fixed when encountered is important.

In an enterprise, you also need to ask if there is a good company behind the project from whom you can get a support agreement, training, consulting, etc… In that case, maybe the above questions are irrelevant.

Of course, being open source, you also should ask: Can I fix it myself and submit the patch back? The communities love it when you do that.

Update: (12 hours later) I just wanted to point out that I DO agree with most of the comments posted below. Raw numbers are kind of pointless and are very hard to do comparisons. They can be interpreted many ways. For example, if you look in the last table, CXF had 441 bugs logged in the last year whereas Axis2 only had 332. Thus, an argument could easily be made that CXF is buggier than the others. Even if I pull out the JAX-RS and DOSGi bugs, it only drops to 366.

However, the one thing that I think IS comparable are the percentages on that last chart. The CXF team is resolving over 85% of the bugs that are logged. The Metro folks are resolving over 80%. Those are pretty respectable numbers. Again, that third question is important. If you do hit a bug, how likely is it to be fixed? 40%? 80%?

Of course, with Open Source, the answer can easily be 100% chance: fix it yourself and submit a patch.

Chris Pepper: Human Psychology: Laziness & Efficiency

2009-11-06T00:30:00+00:00

When I started my current job I got a desk in a large multi-person office. I've been printing to a high-speed printer/copier (which actually does decent scanning with functional OCR). There were a couple LaserJets and a fax machine elsewhere in my room, and a couple more LaserJets in the other multi-room office in our group.

A few weeks ago they moved the LaserJets and fax machine in my office, so they're now in between me and the high-speed printer/copier. Since then, I find myself walking past the LaserJets en route to the printer/copier, and wondering if I should print to them instead, to save myself the longer walk. But I don't because the high-speed jobbie is more efficient (green).

Of course, the walk I'm now mildly annoyed by hasn't changed, and I previously appreciated it because the shortest walk was to the best printer. So the movement of the LaserJets has significantly changed my perception of the (walk to the) printer/copier, and the significance of relative positioning is demonstrated.

Midly amusing, at least to me.

Eran Chinthaka: Apachecon 2009 Web services talks

2009-11-05T23:31:44+00:00

Thought of putting out the talks I did in Apachecon.

First talk "Axis2 Landscape" gives an introduction to Apache Axis2 project and also provides some information on the architecture of Axis2.

In the second presentation, me and Afkham Azeez talked about some use-cases where Axis2 and Apache WS projects were used.

Axis2 Landscape

View more presentations from eran.chinthaka.

Web Services in the Real World

View more presentations from eran.chinthaka.

Justin Mason: Links for 2009-11-05

2009-11-05T23:05:03+00:00

Introducing Resque - GitHub : github’s take on a good, distributed queueing system in Ruby
(tags: ruby github queueing ipc resque)

Sam Ruby: Too Funny

2009-11-05T23:03:03+00:00

Hi Ellen!

I’m sure that there is a rhyme or reason to this, but for the life of me I can’t imagine what it would be. If anybody has any insight as to what it might be, suffice it to say that I am very curious at this point.

Jeremy Quinn: Spectators [Flickr]

2009-11-05T21:42:09+00:00

sharkbait posted a photo:

Guy Fawkes Night, Brockwell Park, 2009
A reminder of our grisly past – of conflict between Catholics and Protestants.

Jeremy Quinn: Whoosh ! [Flickr]

2009-11-05T21:41:30+00:00

sharkbait posted a photo:

Guy Fawkes Night, Brockwell Park, 2009

Jeremy Quinn: Aaaaaaaaah ! [Flickr]

2009-11-05T21:40:39+00:00

sharkbait posted a photo:

Guy Fawkes Night, Brockwell Park, 2009

Jeremy Quinn: Ooooooooh ! [Flickr]

2009-11-05T21:39:10+00:00

sharkbait posted a photo:

Guy Fawkes Night, Brockwell Park, 2009

Gianugo Rabellino: Time for some news: BPmo is on his way

2009-11-05T21:02:58+00:00

Whoa – six months have passed since my last post, clearly there is something wrong with my blogging schedule. It’s not like I’m lacking interesting stuff to write about, it’s just that free time has become quite an abstract concept over here: let’s just say that I’m an ecstatic new father, a busy man and someone who hit the golf course just once this year (and yes, I was crap). Life is being extremely good to me, though, so I guess this is a great time to share some news. A picture is worth a thousand words, they say:

In case you are wondering, yes, that is a picture of our upcoming second child. BPmo (you might remember we have a twist for code names: for the curious in you, this is our abbreviation of “Bambino Piccolissimo”) is about to enter his 13th week, and seems to be keeping with the tradition of doing a lot of kicking around.

Mom is fine, and we are overjoyed to say the least, despite being more than a bit surprised by the quite unexpected news of doubling our joy a mere 8 months after Alessandra joined us (by the way, she’s a darling). Stay tuned and keep this blog subscribed – chances are I might write something every now and then, just don’t expect much from here to May 15th: keeping with the tradition, you will be the first to know.

The Apache Way: The Apache Way - Openness

2009-11-05T20:00:00+00:00

Openness

What it means

The concept of doing as much work as possible in public is fundamental to The Apache Way. For a community to best work and grow, it's technical work must happen in the open.

Open communication promotes community growth. Having existing and past technical discussions and decisions available in the mailing list archives makes it easier for new users to understand the project and the choices the community made to get where it is today.
Open communication ensures community health. Having every email you write to the project lists be published may be unnerving to some at first, but it's crucial to ensure that the whole community can contribute to the work. This also ensures that community members in different regions, or who work on different schedules, can still participate.
Face to face meetings must have results published and voted on. While in-person meetings or telephone conferences are sometimes held to increase collaboration, the results of any meetings must be published to the project mail lists. Any decisions made off-list must be ratified by a vote or lazy consensus on the public lists to be valid.
Open work ensures everyone can participate. Having all of the technical discussions, consensus building, and code and documentation work happen in the open ensures that everyone can participate and everyone – contributors and just lurkers alike – can learn from the process and understand where the project is going.
Open work ensures our projects remain neutral. A healthy community has some diversity, and ensuring that all work on the project happens in the open means that no one set of contributors or no corporation or other organization can command the project or use it solely for their own ends. Everyone can see what the project is doing and who is advocating what within the project.
Open communication allows for oversight. Within the ASF, there are a few core values that we expect all our projects to follow. Having the project's work happen in the open ensures that the board and the PMC can review what's happening to ensure the core values are accepted and followed.
Open status ensures that everyone can know what's going on. New users don't need to know who to ask to learn about the project: everything is on the mailing list, the archives, the website.
Open lists promote open reputations. Merit within a community is gained through open work within that community. While each community has it's own standards for levels of merit (i.e. at what point an individual may be voted in as a committer), open lists mean that all of a person's work on other communities is also visible.

Matt Raible: Happy Birthday Abbie!

2009-11-05T18:22:06+00:00

Today marks the 7th anniversary of Abbie's Birthday. Happy Birthday Kiddo!

I have to say that this year is quite a bit better than last year, especially since I got laid off on her birthday last year.

To commemorate this special occasion, I pulled out some pictures from the archives. Here's one of her and I on her first weekend, as well as her first cheerleader outfit.

To see how Abbie has grown up over the years, see past Happy Birthday posts: #1, #3, #4, #5 and #6.

Howard M. Lewis Ship: Tapestry 5: Java Power, Scripting Ease (ApacheCon 2009)

2009-11-05T16:51:27+00:00

I've uploaded my presentation from ApacheCon 2009. Of coure, the fun parts are the embedded screen casts, and you need to see me live to get that part!

Tapestry 5: Java Power, Scripting Ease

View more documents from Howard Lewis Ship.

Sam Ruby: Web3D

2009-11-05T14:06:34+00:00

Instructions:

Download Firefox 3.7
tar xjf firefox-3.7a1pre.en-US.linux-x86_64.tar.bz2
cd firefox
killall firefox
./firefox
Navigate to about:config, click I’ll be careful, I promise!
Enter webgl in the filter. Double click webgl.enabled_for_all_sites

Come back here, and rotate the image below using your mouse.

View source. Note the use of a namespace and mixed case element and attribute names. We will be discussing this tomorrow.

Stephane Bailliez: Ubuntu 9.10 Server 64 bits in VMWare 7

2009-11-05T08:39:41+00:00

This was not exactly a home run and while the install went smoothly – I was actually surprised to not have any questions during the install – the result left a bit to be desired. I realized something was wrong when I tried to have shared folders activated..it just didn’t show under /mnt/hgfs and vmware tools were supposedly installed correctly during the initial install…but it didn’t appear so.

So next step was to actually access the cdrom..which did not work, it was not mounted automatically and fstab ended up with 2 cdroms (not sure why) with /media/cdrom0 mapped to /dev/scd1 and /media/cdrom1 to /dev/scd0.

In addition, booting the instance, vmware complained about the floppy disk not accessible even though it was the usual default ‘autodetect’, and it seems to cascade into the entire disappearance of cdrom devices…oh well.

I kinda took a shot in the dark and modified fstab to keep only /media/cdrom0 mapped to /dev/scd0, manual mount..miracle I could see something.. then proceeded to reinstall vmware tools and I can now see shared folders… and all seems to be going well…for now.

Ben Laurie: Another Protocol Bites The Dust

2009-11-05T07:03:37+00:00

For the last 6 weeks or so, a bunch of us have been working on a really serious issue in SSL. In short, a man-in-the-middle can use SSL renegotiation to inject an arbitrary prefix into any SSL session, undetected by either end.

To make matters even worse, through a piece of (in retrospect) incredibly bad design, HTTP servers will, under some circumstances, replay that arbitrary prefix in a new authentication context. For example, this is what happens if you configure Apache to require client certificates for one directory but not another. Once it emerges that your request is for a protected directory, a renegotiation will occur to obtain the appropriate client certificate, and then the original request (i.e. the stuff from the bad guy) gets replayed as if it had been authenticated by the client certificate. But it hasn’t.

Not that the picture is all rosy even when client certificates are not involved. Consider the attacker sending an HTTP request of his choosing, ending with the unterminated line “X-Swallow-This: “. That header will then swallow the real request sent by the real user, and will cause any headers from the real user (including, say, authentication cookies) to be appended to the evil request.

It’s obviously going to take a little while for the world to patch this – and since the news is spreading like wildfire I’ve put up a patch to OpenSSL that bans all renegotiation. I’m sure an official release will follow very shortly.

Note that the patch is against the head of the OpenSSL 0.9.8 development tree (that is, it is against 0.9.8l-dev). You may have to do a little work to patch against other versions. And if you intend to deploy this patch permanently, please change at least the textual version of the version number, which you can find in crypto/opensslv.h. Also note that if you need renegotiation for your site to work, I have no solution for you, other than you redesign your site. Sorry.

Edward J. Yoon: Subversion Submitted to Become a Project at The Apache Software Foundation

2009-11-05T06:03:51+00:00

Subversion Submitted to Become a Project at The Apache Software Foundation

Today, I noticed that Subversion proposal/vote was opened in the general mailing list of Apache Software Foundation.

Hi all,

The Subversion Corporation decided recently to submit Subversion to
the Apache Software Foundation. I've sent the initial proposal to
Apache's Incubator project requesting the move (see below).

There are a lot of ramifications to this step. It would take me quite
a while to write this email if I detailed this stuff. In short, there
will be *no change for users*. This will primarily impact the
development community.

Please stay tuned for more info!

Thanks,
-g

버전 관리툴로 잘 알려진 Subversion이 Apache Project로의 제안이 제출되었습니다. 아직 투표가 진행중이지만, 거의 100% Apache Subversion이 확정된것 같네요. :) 오픈소스는 ASF가 짱 먹을려나 봅니다.

Matt Raible: Testing GWT Libraries with Selenium and Maven

2009-11-05T05:27:44+00:00

On Tuesday, I wrote about Running Hosted Mode in GWT Libraries. Today I added an additional module to our project to run Selenium tests against our GWT library. In the process, I discovered some things I needed to modify in my GWT library's pom.xml. I'm writing this post so others can use this setup to write GWT libraries and package them for testing with Selenium.

First of all, I noticed that when you're using the GWT Maven Plugin with a JAR project, it doesn't automatically run gwt:compile or gwt:test in the compile and test phases. I had to explicitly configure the compile goal to run in the compile phase. I also had to add <webappDirectory> to the configuration to compile the JavaScript files into the war directory.

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>gwt-maven-plugin</artifactId>
    <version>1.1</version>
    <configuration>
        <module>org.appfuse.gwt.core.CoreUI</module>
        <runTarget>index.html</runTarget>
        <webappDirectory>war</webappDirectory>
    </configuration>
    <executions>
        <execution>
            <phase>compile</phase>
            <goals>
                <goal>compile</goal>
            </goals>
        </execution>
    </executions>
</plugin>

To package the generated JavaScript and index.html in the JAR, I added the following <resources> section to the maven-resources-plugin configuration I mentioned in my previous post.

<resource>
    <directory>war</directory>
    <includes>
        <include>core.ui/**</include>
        <include>index.html</include>
    </includes>
</resource>

In addition, I discovered some javax.servlet.* classes in my JAR after running "mvn package". I believe this is caused by the GWT plugin sucking these in when it compiles my ProxyServlet. I excluded them by adding the maven-jar-plugin.

<plugin>
    <artifactId>maven-jar-plugin</artifactId>
    <configuration>
        <excludes>
            <exclude>javax/servlet/**</exclude>
        </excludes>
    </configuration>
</plugin>

After doing this, I was able to publish my JAR with all the contents I needed to run Selenium tests against it.

Testing the GWT Library with Selenium
The module that contains the Selenium tests is a WAR project that uses war overlays, Cargo and Selenium RC. You can read about the Maven setup I use for running Selenium tests in Packaging a SOFEA Application for Distribution.

The major difference when testing a JAR (vs. a WAR), is I had to use the maven-dependency-plugin to unpack the JAR so its contents would get included in the WAR for testing. Below is the configuration I used to accomplish this:

<plugin>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <id>unpack</id>
            <phase>generate-sources</phase>
            <goals>
                <goal>unpack</goal>
            </goals>
            <configuration>
                <artifactItems>
                    <artifactItem>
                        <groupId>org.appfuse</groupId>
                        <artifactId>gwt-core</artifactId>
                        <version>1.0-SNAPSHOT</version>
                        <type>jar</type>
                        <overWrite>false</overWrite>
                        <excludes>META-INF/**,org/**,javax/**</excludes>
                    </artifactItem>
                </artifactItems>
                <outputDirectory>
                    ${project.build.directory}/${project.build.finalName}
                </outputDirectory>
            </configuration>
        </execution>
    </executions>
</plugin>

Hopefully this will help you develop GWT libraries and run Selenium tests against them. If you have any suggestions for simplifying this configuration, please let me know.

NOTE: I did considering a couple of other options for running Selenium tests against our GWT library:

Add something to the existing project that 1) creates a WAR and 2) fires up Cargo/Selenium in a profile to test it.
Create the tests in a GWT (war) project that includes widgets from the library.

I decided on the solution documented above because it seemed like the best option.

Assaf Arkin: Necktie: dress to impress

2009-11-05T03:59:27+00:00

How Necktie Happened

Necktie came about when I needed to automate server configuration for Apartly. We run on EC2, which means instances for production, for staging, and for short-lived tasks like testing out new configuration or performance benchmarking.

To get the all instances configured the same way, I wrote a Capistrano recipe. I quickly hit the limits of that approach: it would take too long to copy individual files (configs, scripts, etc) from the local box. And I would have to maintain, in addition to the local recipe, a Ruby script to orchestrate everything on the remote machine.

So the next logical step was to pre-package everything — the scripts, configurations, binaries — into a Git repository and have Capistrano clone it on the remote server and run a main script there. It’s similar to cap deploy, except the code you’re deploying and running does things like reloading Nginx with a new configuration, mounting an EBS volume for MySQL, installing cron jobs, stuff like that.

It worked extremely well, but quickly developed into a mishmash of common features and application-specific tasks, part in the application’s own recipe directory, part in a separate Git repository I named necktie. It was begging for extraction.

A few iterations later, and Necktie was born. Necktie is basically a common line tool based on Rake and Git, and a Capistrano task for running it remotely.

Necktie In 15 Seconds

To manage a server configuration, you create a Git repository with a Necktie file in it. You use the same repository to hold other files used for setting up a server: config files, cronjobs, scripts, Ruby gems, etc.

If you have more than a handful of tasks you can split them into individual files and place these in the tasks directory.

A Necktie repository will look something like this:

$ tree .necktie
.necktie/
|-- Necktie
|-- etc
|   |-- cron
|   |   `-- snapshot
|   |-- god.rb
|   |-- init.d
|   |   `-- unicorn
|   `-- nginx
|       `-- unicorn.conf
|-- gems
|   |-- memcache-client-1.7.5.gem
|   |-- mysql-2.8.1.gem
|   `-- unicorn-0.93.3.gem
`-- tasks
 |-- app.rb
 |-- deploy.rb
 `-- db.rb

Separately, I have a Capistrano recipe which contains the following two lines:

require "necktie/capistrano"
set :necktie_url, "git@example.com:necktie"

The first line adds the cap necktie task, the second line tells it where to find the necktie repository. Of course, you should be using your own Git repository.

To configure new servers and upgrade existing ones:

$ git push && cap necktie

Life couldn’t be simpler.

Tasks 101

The heart of your Necktie repository consists of tasks that configure and setup a server instance. You can mix Ruby and shell commands to write tasks like:

# Create /etc/init.d/unicorn so you can sudo service unicorn restart
cp "etc/init.d/unicorn", "/etc/init.d/"
update "/etc/init.d/unicorn", /^ENV=.*$/, "ENV=#{Necktie.env}"
chmod 0755, "/etc/init.d/unicorn"
services.restart "unicorn"

In addition to good old Ruby you’ve got direct access to all the FileUtils methods (cp, mv, chmod, etc), Rake’s sh method and FileList, all of Rush, and a bunch of niceties like read/write/append/update for processing files, install_gem and a thin API around the Linux service command.

Besides bringing fresh servers up to speed, you’ll also want to use Necktie to upgrade production server with least amount of down time. To make that easier (and users happier), write tasks that only execute when necessary.

For example, here’s a task that changes the default memcached configuration to listen on all IPs (I’m running this behind a firewall). It’s designed to work if memcached is not running (and in doing so start it), or if memcached is running with the wrong IP address:

task :memcached do
  # Out of the box, memcached listens to local requests only.
  # Allow access from all servers (in the same security group).
  unless processes.find { |p| p.cmdline[/memcached\s.*-l\s0.0.0.0/] }
    update "/etc/memcached.conf", /^-l 127.0.0.1/, "-l 0.0.0.0"
    services.restart "memcached"
  end
end

The next task updates an Nginx configuration file and reloads its whenever the configuration file from the Necktie repository (that would be “etc/nginx”) is newer than the configuration file installed on the server (that would be “/etc/nginx”):

file "/etc/nginx/sites-available/unicorn.conf"=>"etc/nginx/unicorn.conf" do
  cp "etc/nginx/unicorn.conf", "/etc/nginx/sites-available/"
  ln_sf "/etc/nginx/sites-available/unicorn.conf", "/etc/nginx/sites-enabled/"
  sh "service nginx reload"
end

Here’s another example that will only mount a volume once:

task "/vol" do
  sh "mount /vol"
end

And you can easily express dependencies and use smaller tasks to compose larger tasks:

task :unicorn=>:memcached # unicorn runs our app, so needs memcached
task :nginx=>:unicorn # nginx is front-end to unicorn
task :app=>[:environment, :nginx, :postfix]

Role play

You probably have servers configured for more than one role, at least app server and db server. I recommend using the same set of roles for both Capistrano and Necktie, then you can run commands like this:

$ cap necktie ROLES=app

This instructs Capistrano to run the necktie task against all servers in the role app, and only these servers. Capistrano will invoke the necktie command with the single argument app, telling Necktie to only execute that one task. You just need an aggregate task for each role name.

I have one task called app that orchestrates all the tasks necessary to configure a server for hosting the Web application, and another task called db that sets up MySQL server and EBS snapshots. For convenience I placed them in tasks/app.rb and tasks/db.rb, respectively, and because app is the default role, also defined:

task :default=>:app.

Why Necktie, why not …?

I looked at Puppet, but it speaks some language I don’t understand. I am very well versed in Ruby, Bash and Rake, and that combination works well in so many places, so why not here?

The complexity of your configuration system should be proportional to the complexity of they system you’re configuring. I have to manage a handful of EC2 instances, all running Ubuntu, in three different roles. Chef demanded too much of my time in the kitchen.

Necktie is minimalist, straight Ruby, and uses Git for storage and distribution. Just right.

Image by 2bib.de

Rich Bowen: Happy 10th Birthday Apache

2009-11-05T03:15:37+00:00

I do a podcast called Feathercast, about technologies and people within the Apache Software Foundation. I do this for a number of reasons.

I love playing with technology, even when I don’t really understand it. Using it is the best way to understand it, and I’ve learned a lot about audio recording in this process, although I’m still far from an expert.

I get to talk with some amazing people, and ask them about stuff that’s truly fascinating.

And I enjoy educating. I like to weasel out the important details and teach people about things that they might otherwise have dismissed as unimportant. I like taking complicated ideas and explaining them in terms that everyone can understand.

In other words, it’s a mixture of selfishness and altruism, as are all worthwhile human endeavors. If we’re doing something entirely for ourselves, that’s no good, but it’s also important to have a passion for something, and for it to be fun.

Coincidentally, these are the reasons that I’m involved in the ASF. They happened in a different order - I got involved because I found an interesting technology and started writing about it. But along the way I’ve met some amazing people - Douglas Adams, Brian Behlendorf, Arthur C Clarke, Sanjiva Weerawarana, Mark Shuttleworth, Ken Coar, Deepal Jayasinghe, Larry Wall, and so many others it’s impossible to list them. Some of these people I’ve come to consider friends.

I’ve also had the opportunity to be involved in amazing technologies that have changed the way we communicate, play, and do business. The Web is, of course, built on generations of advances, and even more amazing things are to come, but it’s been a fascinating ride to be part of that.

Apache, and other open source technologies that I’ve had the opportunity to be involved in, have changed the world, and I got to be part of that, because they are open source, where the willingness to participate is rewarded with the permission to participate, unlike so many other parts of our world. We get to be a part of things that matter, and the barrier to entry is that willingness to participate and make a difference.

It’s a great honor to be a member of the Apache Software Foundation. It’s a badge that I wear with pride, both because I know how hard I worked to achieve it, and because I’ve seen the other amazing things that the ASF has accomplished.

Happy Birthday, Apache. Here’s hoping the next ten years are as exciting as the last ten, and that I get the chance to be even more involved than I have for the last ten.

Yoav Shapira: Boston Frisbee Halloween extravaganza!

2009-11-05T01:36:57+00:00

I've written about Boston Frisbee before. It's the awesome group that's open and welcoming to everyone, which plays frisbee three times a week. I play sometimes on Sundays, on the grounds of the Boston Common. Logistics and other details are available.

On Halloween weekend, they play a game in costumes. There are some funky special rules added for some points, contests, and more fun stuff. This past Sunday both Alli and I played in our costumes, and we had a blast.

There are a bunch of good pictures now available on SmugMug and Facebook. I'm the orange M&M, and Alli is the yellow belly dancer.

Carlos Sanchez: Continuum-ruby

2009-11-05T00:09:51+00:00

continuum-ruby is a Ruby library to interact with Apache Continuum, using the XML-RPC interface and enabling access to the working copy directories. continuum-ruby is now available in the Continuum Sandbox.

More info on the Continuum XML-RPC interface:

Example

continuum = Continuum::Continuum.new("my.continuum.host", 8080, "admin", "password", "/continuum")

# xml-rpc interface

xml_rpc = Continuum::XmlRpc.new(continuum)

ok, result = xml_rpc.build_project(1)
error = Continuum.parse_error(result) if !ok

# getting working copy files

working_copy = Continuum::WorkingCopy.new(continuum)
test_results = working_copy.get(1, "target/surefire-reports", "emailable-report.html")

files = working_copy.dir(1, "target")
files.each do |file|
  file_content = working_copy.get(1, "target", file)
end

Justin Mason: Links for 2009-11-04

2009-11-04T23:05:04+00:00

SBSettings : good overview of this jailbreak app
(tags: iphone jailbreak hack software apple sbsettings unlock)
Why would I want to jailbreak an iPhone 3GS? : Ask MeFi thread, mostly recommending tethering and SBSettings
(tags: sbsettings jailbreaking askmefi metafilter iphone apple)
Subversion Submitted to Become a Project at The Apache Software Foundation : woot!
(tags: svn subversion asf apache open-source incubator)

Mads Toftum: Autumn has arrived

2009-11-04T22:23:53+00:00

I went on yet another walk to one of the nearby parks and found a lot of colors had changed.

Luciano Resende: ApacheCon 2009 Session : SCA, Java EE, Spring, Web 2.0 and Cloud Come Together - Service assembly with Apache Tuscany SCA

2009-11-04T22:16:00+00:00

ApacheCon US 2009 has started and I'm done with my first Apache Tuscany session.

SCA, Java EE, Spring, Web 2.0 and Cloud Come Together - Service assembly with Apache Tuscany SCA
Wed, 04 November 2009 11:00, by Luciano Resende

Slides are now available

Tuscany cloud tutorial source code is available in Tuscany SVN at sca-cloud-tutorial sandbox.

The application integration sample (a.k.a Travel Sample) is available in Tuscany SVN at travel-sample sandbox.

Mads Toftum: Recipes: Sottofiletto di Manzo al Pepe Verde and Pere al Vino Rosso

2009-11-04T22:11:25+00:00

Recipe: Sottofiletto di Manzo al Pepe Verde

Recipe is for 8 people.

1.2 kg fillet of beef
1 tbsp neutral oil
Salt

Heat the oven to 180C.
Brown the meat on a frying pan and rest in the pan for 10 minutes.<br > Roast the meat for 10 minutes, rest it outside the oven for 10 minutes
Roast the meat for 10 minutes, rest it outside the oven for 10 minutes (yes, that repetition was intentional).
Return the meat to the oven and roast until done (depends on size and whether you like your meat to still be moving or not).
Rest for at least 15 to 20 minutes before slicing

Sauce

1 tin Madagascar peppers (small tin brined - I think the size is about 100g)
1 tbsp mustard
20 g butter
0.3 L double cream
0.05 L brandy
1 branch rosemary
1 branch sage
Salt

Heat a frying pan with butter, mustard, sage and rosemary.
Discard the brine from the peppers and dry, and add to the pan when the butter starts to brown.
Flambe with the brandy.
Add cream and reduce for 3 minutes.
Remove the sage and rosemary and pour the sauce over the beef before serving.

NOTE: being traditional italian, it would be served as just one course among many and with no sides. For a little extra kick, you could let a bit of the brine go into the sauce as well, but be careful as the pepper berries still make their presence known when you bite into one.

Pere al Vino Rosso

Ingredients are for 8 people.

8 pears
1 bottle redwine
175 g sugar
0.5 L water
2 sticks cinnamon
2 whole cloves

Peel the pears, leaving the stalk on.
Place the remaining ingredients in a saucepan and add the pears.
Cook for about 20 minutes until a bit softer, but still leaving a bit of bite.
Remove the pears and reduce the liquid until it goes syrupy. The picture below shows how the syrup will start forming bubbles right before it's done. Leave it on the heat a few seconds longer and all you'll taste is burnt sugar.
Let the syrup cool off the heat for a bit (timing made that impossible which is why the syrup is not sticking to the pear in the picture above) and pour over the pears before serving.

There's a couple of more pictures from that same round of cooking on flickr.

Luciano Resende: Subversion is being proposed as an Apache Incubator project

2009-11-04T21:53:30+00:00

The CollabNet-sponsored Subversion project and The Apache Software Foundation (ASF) announced today that the award-winning Open Source project has formally submitted itself to the Apache Incubator in order to become part of the Foundation's efforts.

Read the Press Release....

Jan Materne: Getting the Samsung CLX 2160 MFC work under Windows 7

2009-11-04T21:34:32+00:00

My laser printer Samsung CLX 2160 worked very fine under Vista. But now I have upgraded to Win7Ultimate and it does not any more. Ok – new OS, new search for drivers …

I found a new driver on the Samsung page. But after installing I even couldnt print. The OS silently ignored print jobs. I tried to check the settings, but I always get the error message

Then I got an idea: maybe the (default) access rules are too restrictive. So I tried to widen them (Everybody: configure the printer, configure the documents)

And now it works

Sander Temme: ApacheCon US 2009 PGP Keysigning

2009-11-04T20:38:40+00:00

We’ll be doing a PGP Keysigning Session at ApacheCon. If you would like to participate, check out http://wiki.apache.org/apachecon/PgpKeySigning and make sure to mail me your public key before the end of today, Wednesday.

Share this post:

Aidan Skinner: Litl launches!

2009-11-04T20:05:27+00:00

Today we launched our web book, I no longer have to enigmatically raise my eyebrows in response to questions about my job etc.

Can't believe I've only been here for 6 weeks. Feels like so much longer (in a good way).

Anyway, Wall Street Journal article, Reuters, El Reg.

Gratuitous pic of the team (wtf is my hair doing?)

- Aidan

ETA: tech detail heavy post here
ETAA: and another from Lucas here.

Steve Loughran: rollback

2009-11-04T18:03:00+00:00

Colleagues have been coming up, looking at my laptop and snickering, asking how the upgrade went.

Well, I don't understand bootwait; apparently unbuntu does block for the /home mount, and having forced an fsck on bootup I can verify this -so why was sometimes X coming up without it? Other problems. But what happens if you add bootwait to the /home mount? The boot hangs. So if there is a disk you need mounted, you'd better know if the OS already mounts it early, as adding the attribute when it is not needed appears to be bad news

More problematic is the laptop won't resume from a suspend; I spent some time following the wiki guide to debugging suspend problems, but eventually reached the point where I'd had enough.

I have rolled back to Ubuntu 9.04, trying out the 64 bit version in the process. I will keep an eye on the power management bug and maybe try an upgrade when its fixed. Maybe.

Sam Ruby: SubVersion → ASF

2009-11-04T17:46:09+00:00

CollabNet: The CollabNet-sponsored Subversion project and The Apache Software Foundation (ASF) announced today that the award-winning Open Source project has formally submitted itself to the Apache Incubator in order to become part of the Foundation’s efforts.

Rich Bowen: ApacheCon US 2009, days 1 and 2

2009-11-04T17:10:17+00:00

I'm in Oakland for ApacheCon US 2009, and we're about to start the first day of the main conference. Monday and Tuesday were for half-day and full-day training classes. Jim Jagielski and I did the two-day Apache web server training class, with him doing day one and me doing day two.

I've been fighting off a cold for more than a week now, and by the end of yesterday I had no voice left, which was very frustrating, but the class were understanding and forgiving, and Jim bailed me out for the last hour of the day.

Last night we had the members reception, which was great, as always. Then later in the evening I went down to the San Francisco Perl Mongers meeting, and hung out with Julian for a little while.

We're now about 10 minutes late for the start of the opening plenary, and ... here goes.

Sam Ruby: Introduction to Decentralized Extensibility

2009-11-04T17:08:16+00:00

Noah Mendelsohn: This is the presentation I will be giving on 4 November 2009 at the W3C Technical Plenary session on Decentralized Extensibility

Liam Quin: Automatic XML namespaces

Tony Ross: Distributed Extensibility Submission from Microsoft

Chris Pepper: Mac OS X 10.6.1: Screen Sharing 64-bit bug

2009-11-04T15:45:00+00:00

I just found a very aggravating bug in Snow Leopard's Screen Sharing. This wasn't present in Leopard (10.5) or the 10.6 betas I used for connecting to these hosts, but is broken in 10.6.1. Fortunately the fix is straightforward. rdar://7364212 http://openradar.appspot.com/radar?id=109401.

Here is my report, for the next person to hit this bug:

Screen Sharing to Linux `vncserver` fails in 64-bit

I use VNC through an ssh tunnel to connect to 2 CentOS Linux servers.

pepper@teriyaki:~$ alias vncsaba

alias vncsaba='(sleep 4; open vnc://127.0.0.1:5901) & ssh -C -4 -L 5901:127.0.0.1:5901 saba'

This worked a couple months ago, but failed this morning. I could connect, but only saw a white screen.

Interestingly, when I restarted the vncserver, the white screen changed to show the proper Linux desktop, then the connection broke, then the white box came back.

This was repeatable across both Linux servers.

I confirmed that the Linux vncviewer program worked properly -- no white box.

The workaround was to force Screen Sharing to run in 32-bit mode, which avoided the white screen and let me control the Linux sessions normally.

http://www.macosxhints.com/article.php?story=20090916105559390

Aaron and Jenny Farr: I quit

2009-11-04T13:34:42+00:00

I quit my job in HK. I was working from the US, developing lessons for an e-learning company. I’ve been working with this company for almost a year now. It’s not that I didn’t enjoy working from home, or exercising my brain. I simply didn’t have the time to work.

Life in the US is certainly more demanding than HK life, at least for me. Stateside, I don’t have hired help. I have more material things to take care of. I live in a bigger house, which means more cleaning, organizing, etc. Travel opportunities are easier here because we have a vehicle. Everything is just busy!

I certainly don’t sit around and pine for my easy Lamma Island life of swimming and tea sipping. It’s rewarding to be close to family and watch the seasons change. This time, especially since I’m pregnant, is a lovely chance to reconnect with my roots.

Written by Jennifer Farr on Wednesday, November 04, 2009. Permalink.

Adrian Sutton: Conversion for the Web

2009-11-04T11:20:33+00:00

Andrew Shebanow in Open Government and PDF:

The issue at hand is not whether governments should pick HTML or PDF. The issue at hand is whether governments are capable of publishing information at all. Show me an HTML creation tool that creates high quality, standards conformant markup from a Word document or any of the zillions of editing tools that government employees use. Now add in all the tools used by people who submit documents to the government. And all the versions of those tools released in the last 20 years. Now make sure that the HTML/XML works correctly even when the user doesn’t have the right browser or the right fonts installed.

I’ve actually worked with a number of government departments who were looking to move more content online and the content conversion problem is definitely a time consuming and challenging part of the problem. That’s precisely why I wind up getting involved, since EditLive! lets you easily copy and paste content from Word documents and produce clean, compliant XHTML. It can even (optionally) strip out inline formatting and leave just the structure like headings, tables and lists.

Furthermore, EditLive! is actually quite good at making sure the HTML works correctly even when the user doesn’t have the right browser or the right fonts installed, especially when it’s been configured to suit the particular content needs. Even with non-technical business authors this can work very well and is doing so for a significant number of government departments.

That’s not to say it’s the whole solution, there are systems out there where it’s hard to convert the content to HTML and where HTML may not be the best format anyway. Some of those cases may work better with PDF but certainly not all of them. To somehow suggest that PDF is a complete and simple solution to publishing information on the web misses quite a lot of the picture. For example:

How do web site visitors navigate around and get to that PDF data? How do they search and find it? As much time is spent working out navigation structures as it is converting content.
How do you expose information from databases with regularly changing information? Wouldn’t a HTML representation be easier to generate than PDF in most of these cases?

Putting information on the web is not simple and no single technology is going to make it simple. PDF definitely has it’s place on the web, but so does HTML and a number of other formats. PDF doesn’t alleviate compatibility concerns, not all users have a recent enough PDF reader, not all PDF embed all the fonts and when they do it makes the download very large etc and not all PDFs are standards compliant. Putting non-web stuff on the web is always a big, challenging project, so review the available technologies carefully and pick the ones that best achieve your goals. Very few companies have success with just dumping a whole heap of PDFs on a web server.

Stephane Bailliez: Websites I Find Useful

2009-11-04T10:00:17+00:00

So I have been tagged by Ludovic, and while I’m no big fan of this chain exercise, I thought I could at least execute and try to find the websites I actually find useful, I thought that 5 was actually a bit trivial and would lead to mostly redundant listing between people, so I decided to go for 10. There is no specific order.

Google – because I use it for searching information constantly, as well as GMail, Documents, Maps and News on a daily basis
Flickr – A nice place to share photos but also to look for inspiration.
LinkedIn – I’m absolutely terrible at keeping contacts with people, LinkedIn changed this radically for me as it makes the contact information all accessible in one place with an incentive to update it.
TripIt – In the same area, a regular complaint from family and friends is to know where and when I’m going to some places, with TripIt, it made it substantially easier as it will broadcast the information automatically.
Amazon – Most of the books I buy are from this place.
Wetpixel – To keep in touch with what’s happening in underwater photography land
ScubaStore/DiveInn – I tend to buy most of my underwater gear online if I can. Fast and reliable service.
InfoQ – The portal I regularly visit to get some tech news update. Agile articles are a bit overwhelming in the last couple of years though.
Wikipedia – So convenient to read complete information about a topic in a digestible format.
dpreview – To keep an eye on photography-related news
TED – Because some things are worth spreading

I would have loved to have this from people from a much diverse background (ie non-technical), but the sinae qua non condition is that this person actually has a blog, so I do have to fallback to technical people on this one:
Emmanuel, Geir, Leo, Sylvain, Torsten

Jacopo Cappellato: HotWax Media is Gold Sponsor at ApacheCon US 2009

2009-11-04T09:25:34+00:00

We did it again!
HotWax Media is again, after last year's Platinum Sponsorship at New Orleans conference, one of the top names at ApacheCon: we are Gold Sponsor at ApacheCon US 2009, Oakland.
Unfortunately this year I am not able to attend and meet the Apache gents, but for sure HotWax Media will be greatly represented by Mike Bates and Tim Ruppert.
Here is the blog post about this event from HotWax Media blog:
HotWax Media, Gold Sponsor, ApacheCon US 2009

Claus Ibsen: Getting started with Apache Camel webinar part 2

2009-11-04T08:35:00+00:00

This is a blot post on the 2nd part of a webinar series about getting started with Apache Camel.

If you missed the first part then I recommend checking this blog post first.

Scott Cranton, Progress, continues in this 2nd part of the webinar by looking at the different deployment options using Apache Camel.

He shows among others the following different deployment options:

Standalone Java Application
Web Application
Spring Application
ActiveMQ
OSGi in Apache Karaf / Apache ServiceMix

The webinar is listed at the webinar page at http://fusesource.com under webinars.

And its titled - Getting Started with Camel deployments.

During the presentation Scott talks about how Camel compares to other integration products. He mention a link on my blog, which is this one.

And may I add that I personally think its very important, when you compare/investigate products, that you spend equally time looking at the community surrounding the products. As as we say at Apache - Community over Code! I talk about this in more details at my interview at dzone a while back. Another source worth checking out is the links to articles at the Camel site.

Well go grab a big cup of coffee and get ready and watch Scott in action with the 2nd part.

Bryan Pendleton: Coders at Work: Brad Fitzpatrick

2009-11-04T05:46:10+00:00

Chapter Two of the mesmerizing Coders at Work is the interview with Brad Fitzpatrick.

I hadn't heard about Brad Fitzpatrick before I read the chapter, but I was quite familiar with some of his work. I have visited LiveJournal many times, and I have read a fair amount about memcached, and I've looked at a lot of the work that Six Apart have done.

Early in the interview, Fitzpatrick has this to say about testing:

I now maintain so much code, and there's other people working with it, if there's anything halfway clever at all, I just assume that somebody else is going to not understand some invariants I have. So basically anytime I do something clever, I make sure I have a test in there to break really loudly and to tell them that they messed up. I had to force a lot of people to write tests, mostly people who were working for me. I would write tests to guard against my own code breaking, and then once they wrote code, I was like, "Are you even sure that works? Write a test. Prove it to me." At a certain point, people realize, "Holy crap, it does pay off," especially maintenance costs later.

There's a lot of hard-earned experience in that quote.

But what really resonates with me is Fitzpatrick's instinct to trust nothing until it's been proven by fire, by writing and running tests and proving that it works. That sort of question-every-assumption attitude is crucial to the construction of really solid code.

I was also struck by the way that Fitzpatrick didn't get caught in the trap of over-specializing in any one area, but rather was fascinated by all sorts of different software in the complex systems that now exist:

When I was doing stuff on LiveJournal, I was thinking about things from JavaScript to how things were interacting in the kernel. I was reading Linux kernel code about epoll and I was like, "Well, what if we have all these long TCP connections and JavaScript is polling with these open TCP connections that are going to this load balancer?"

I'm rather a generalist myself, and find myself interested in all sorts of different software, from front-ends and UIs to middleware to networking protocols to file systems and database servers. I think there's lots to learn at all these levels, and lots to explore.

I liked Fitzpatrick's very practical suggestions about how to approach a new library of code:

First step, take a virgin tarball or check out from svn, and try to get the damn thing to build. Get over that hurdle.
...
Anyway, once you have one clean working build, kill it, and just make one damn change. Change the title bar to say, "Brad says, 'Hello world.'" Change something. Even if everything's ugly, just start making changes.
...
Then send out patches along the way. I find that's the best way to start a conversation.
...
When I fix a bug in their product the first thing I do is send them a patch in the mail and just say, "What do you guys think of this?"

I think this is a great approach, to get your hands dirty with real code, and then to start discussing actual code, and actual changes, with the community. I've seen this technique be very successful in the Derby community. Dan Debrunner, in particular, is a big supporter of the "let's talk about actual code" approach. It makes things concrete and specific, and it's remarkable how effective it can be to discuss a patch.

I was quite impressed with Fitzpatrick's approach to solving problems in code:

Thinking like a scientist; changing one thing at a time. Patience and trying to understand the root cause of things. Especially when you're debugging something or designing something that's not quite working. I've seen young programmers say, "Oh shit, it doesn't work," and then rewrite it all. Stop. Try to figure out what's going on. Learn how to write things incrementally so that at each stage you could verify it.

The curse of the voodoo change has a strong hold on people. I've seen many an otherwise great engineer say: "I don't understand what's wrong, but I know that if I just make this small change here, the problem goes away. And I'm tired, and I have other things I need to do, and I'm just going to do this and move on."

It's terribly seductive and Fitzpatrick is completely right: you have to be ever vigilant against this false solution, and force yourself to really do the job right.

Yoav Shapira: Book review: Orbiting the Giant Hairball

2009-11-04T02:13:42+00:00

This is not my usual kind of book, but it was a gift from my great friend Jeremy H. And I really, really enjoyed it.

Every once in a while, I get comfortable thinking: "Hey, we're pretty creative here. We do cool stuff, we're open-minded, we experiment. We're still young, we're not afraid to try."

And then I read a book like Orbiting the Giant Hairball, and I realize I'm far from exercising my creative potential, as are most other people.

The full title is Orbiting the Giant Hairball: A Corporate Fool's Guide to Surviving with Grace.

The author is Gordon MacKenzie, who was the Chief Creative Officer (and other, better-titled, roles) at Hallmark.

The book is about how to stay creative in a corporate bureaucracy. I think a lot of the advice is hard to implement, maybe even impractical. Some of it is downright ridiculous and would get you fired. But it's surely entertaining to read about, at least, and there are some great nuggets here.

The author likens big companies to giant hairballs, and the creative people as orbiting those hairballs. As opposed to being inside them, which is the default, or inertia-driven, approach. If you're in orbit, you're intimately related to the hairball, but outside of it, and not part of its most annoying parts. It's an interesting metaphor.

More specifically, the author defines the hairball as "the corporate tendency to rely on past policies, decisions, and processes as a formula for future success." That really strikes a chord with me. It's too easy to fall back on these defaults, especially if they give you some initial success.

And that's just the start of a great book. It's worth reading for humor value along.

But the other unusual thing about this book is its designed. I got this as a gift shortly after raving about my Kindle. I still love the Kindle. But this was the first book I read in a long time that reminded me of the beautiful options available with book design.

I'm not talking about Tufte-style visualizations. Rather, I'm talking about the creative use of doodling, illustrations, variance in fonts and font sizes, unusual layouts, and more typographic approaches. This book, which is self-published, by the way, does it really well.

All in all, an usual book in my library. No spies, no assassins, no Mossad, no sci-fi, no bankers, but really fun to read, and maybe even inspirational at times.

By the way, there was an interesting Fast Company article interviewing the author a couple of years ago, for the curious: How Is Your Company Like A Giant Hairball?

Yoav Shapira: Wine review: 2007 Crochet Sancerre

2009-11-04T02:00:23+00:00

Usually I write wine reviews about wines I like, or wines I love. I want to remember them, for future purchases, investments, and recommendations to friends.

This one is an exception. This 2007 Dominique et Jeanine Crochet Sancerre was not good. We did not enjoy it, and I don't recommend it.

It's bland, boring. Not really refreshing, not really powerful, doesn't quite nail any fruit. Just meh.

I'm writing this because I had higher expectations for this wine, based on reviews and reading. Oh well, live and learn ;)

Jay D. McHugh: Goin back to Cali...

2009-11-04T00:58:59+00:00

I am in California.

This is the second time that I have been in this state.

The first time was over fifteen years ago. And I was here to see how a software company was planning on translating their product from a character based program that ran from a command line in either DOS or _nix - to a windows program.

They were going to try to use a program to translate a BASIC language system to Visual Basic. But the program required a person to make sure that the individual programs were written according to a set of programming standards.

They almost never were - so they ended up doing a substantial rewrite and forced those that had written customizations to write them all over again.

This time, I get to attend the 10th anniversary ApacheCon.

Over the past ten years, the Apache foundation has grown from a small group of people who forked the code from the NCSA web server - to an international group of programmers and users who develop and use a growing set of software projects (currently more than 60 and growing).

About three years ago, my day job gave me the opportunity to develop a substantial new system that would eventually replace a number of scattered information systems that spanned spreadsheets and flat file databases. It would also integrate that information with the company's accounting system.

In trying to figure out the best platform for developing this new system I stumbled onto WebSphere community edition (WASCE) and through it - Apache Geronimo.

I was hooked. Here was an environment to develop for that was scalable, standards based, open source, fast, ... everything I could hope for.

Through Geronimo - I found a number of other projects that are integrated by Geronimo. And each of them was the same - open communities that seek feedback and encourage participation.

I do not know how many people are reading this. Or how many of you are involved in software development. But it is an amazing thing to find people spread out across the whole world who are passionate enough to give away their time and energy developing and/or supporting software.

Last time in California turned out to be a moderately interesting waste of time.

This time, nothing has really started yet - and I am already excited to get to be a part of something so bold and (at least in my experience) unique.

This is, in a word...

Awesome.

Justin Mason: Links for 2009-11-03

2009-11-03T23:05:03+00:00

Spiritual search turns into a stampede as impatient lose faith in double visionaries - The Irish Times - Mon, Nov 02, 2009 : hilarious article on the BVM-witnessing hysterics in Knock. ‘if you looked hard enough, you could indeed discern a face in the play of light and shadows. When I squinted a certain way, I thought I could make out Bruce Forsyth.’
(tags: mayo religion hysteria funny bruce-forsyth bvm fortean)
Structural Regular Expressions : ‘The current UNIX text processing tools are weakened by the built-in concept of a line. There is a simple notation that can describe the `shape’ of files when the typical array-of-lines picture is inadequate. That notation is regular expressions. Using regular expressions to describe the structure in addition to the contents of files has interesting applications, and yields elegant methods for dealing with some problems the current tools handle clumsily. When operations using these expressions are composed, the result is reminiscent of shell pipelines.’ Paper by Rob Pike, via adulau. intriguing
(tags: sregex via:adulau regexp rob-pike regex library text structural parsing)
sregex - Structural Regular Expressions : ‘The sregex module implements Structural Regular Expressions.’ Python, Apache-licensed
(tags: sregex python via:adulau regexp robpike regex library text structural parsing)
The Rise and Fall of the Hobbyist Game Programmer : great article on the 80’s one-man shareware game hobbyists (via Walter)
(tags: 1980s games history programming nostalgia geek gaming hobbies coding 6502 c=64)

Nick Kew: Revisiting Apache 2.0 proxy

2009-11-03T22:45:41+00:00

I have today revisited the reverse proxy on Apache 2.0 (for which mod_proxy_html was originally written).

The good news: the current versions of mod_proxy_html (3.1.2) and mod_xml2enc (1.0.3) build and work nicely with Apache 2.0. I have hitherto recommended Apache 2.0 users mod_proxy_html 2.5 as the ’safe’ solution.

The bad news: working with Apache 2.0’s proxy just seems incredibly limiting, and calls for a whole bunch of hacks/workarounds. I’d forgotten that …

(not that 2.2 is free of them – looking forward to 2.4 and the expression engine).

J. Chris Anderson: How CouchDB Treats the Disks

2009-11-03T22:45:20+00:00

Blogs are pretty much append-only. Most of the time you add new posts, sometimes you edit recent ones. There are new comments.

CouchDB's file format is also append-only. This doesn't make it special, lots of databases have used similar techniques before, but it does make it more like web data.

It also makes it smooth for the disk, because the disk doesn't have to seek for writes, and most reads are from file-system cache.

Here's some slides:

Intro to CouchDB's Append Only B-Tree (9MB pdf) Feel free to reuse with attribution.

Btree Nosql Oak

View more documents from Chris Anderson.

Apache Wicket Community News: London Wicket Event November 21st

2009-11-03T22:24:13+00:00

Something special is brewing in downtown London on Saturday, 21st November. jWeekend is organizing a very special event at the iconic Foyles Bookshop in central London. Join core committers Matej, Alastair, Jeremy and Martijn together with WiQuery gurus Richard and Lionel for an afternoon of intellectual Wicketness. Join us for some very interesting, high quality presentations [...]

Sander Temme: My ApacheCon US 2009 Wishlist

2009-11-03T20:07:14+00:00

Get Apache HTTP Server building again on Gump (which involves losing the dependency on the Apache Portable Runtime Utility library, which was folded into APR proper)
Get @pgollucci what he needs on clarus.apache.org, and work on the future of that box
Talk about Apache 2.4, and what is still needed to get that out the door. Then, maybe start talking about figuring out what 3.0 is going to be like
Prepare for the Keysigning — which may mean creating a new PGP key
Prepare for my presentation on Thursday
Do some httpd hacking. Perhaps pull in the ECC patch that has been sitting in Bugzilla

Sagara Gunathunga: ASF Big Feather Birthday Bash at Aeturnum

2009-11-03T19:39:31+00:00

According to the "Raise a Glass to Apache" open invitation we wanted to have a event within our office. In Aeturnum we use number of Apache software within our development cycle, also some of our people already contributing to Apache projects in various ways.

So we take this moment to join with ASF to celebrate 10th anniversary and also to encourage people to contribute for ASF projects . With the support of our management we have ordered some ASF contributor badges to distribute among our people , In addition to that we got specially designed birthday cake.

Other than the party we had two presentation called " Revolution of FOSS" and "Apache -Community over code" to give some introduction about FOSS and ASF.

You can find "Apache -Community over code" presentation from here

[ Note - Above presentation is created using several resources and slides available with Apache and ApacheCon web sites and I just modified them according the the event]

Bryan Pendleton: JUnit, tearDown, and uncaught exceptions

2009-11-03T19:31:52+00:00

I know this, I've known it for a while, and still I stumble over it.

I tend to generally declare my JUnit test cases as


public void testXXX()
  throws Exception
{
}

Within my test case code, I then typically don't catch any exceptions, unless I'm specifically testing that a particular expected exception is thrown. Instead, I simply allow any unexpected exceptions to be thrown out of the test case, and caught by the JUnit infrastructure, which decides that a test case which terminated with an uncaught exception is an error, and JUnit reports the uncaught exception in the output.

However, there is a gotcha, and it involves the tearDown method. If a particular test suite uses the setUp/tearDown paradigm to perform common initialization and termination functions, then it is crucial that these methods themselves must be cautious with respect to exceptions.

Because if:

your test case terminates with an uncaught exception,
and then your tearDown method terminates with an uncaught exception,

then it is the tearDown exception which "wins"; i.e., it is the exception which is shown in the JUnit output.

This can completely fool you into a wild goose chase of looking at the wrong problem.

In a way, I think this is a mistake in JUnit; I wish it reported the uncaught exception from the test case in preference to the uncaught exception from tearDown, or even better I wish it reported both exceptions.

But, for now, the best thing to do is to ensure that your tearDown methods are extremely careful, and never terminate with uncaught exceptions.

Bertrand Delacretaz: JCR in 15 minutes

2009-11-03T18:02:23+00:00

We had a great NoSQL meeting yesterday evening colocated with ApacheCon. Thanks Jukka for organizing!

I was in track B for the second part, and found it very interesting to compare three different approaches to non-relational content storage: MarkLogic server, JCR and Pier Fumagalli’s Lucene+DAV technique.

I also quite liked Steve Yen’s “horseless carriage” way of looking at NoSQL. Defining things by what they are, as opposed to what they are not, sounds like a good idea.

I gave a short talk about JCR, find the slides below. Of course, as usual, they’re not as good as when I’m here to talk about them ;-)

Planet Apache

Bryan Pendleton: Google have open-sourced their JavaScript library

Davanum Srinivas: Better RSS feed for IBM WebSphere Application Server forum

Matt Raible: User Interface Schema Definitions

Luciano Resende: ApacheCon 2009 Session: Applying OSGi after the fact

Ben Laurie: SSL MitM Attack, Part 2

Claus Ibsen: How buggy is your integration stack?

Matt Raible: Consulting, SOFEA, Grails and GWT at next week's Denver JUG

Bryan Pendleton: Ant integration with application servers is too hard

Daniel Kulp: How buggy is your SOAP stack

Chris Pepper: Human Psychology: Laziness & Efficiency

Eran Chinthaka: Apachecon 2009 Web services talks

Justin Mason: Links for 2009-11-05

Sam Ruby: Too Funny

Jeremy Quinn: Spectators [Flickr]

Jeremy Quinn: Whoosh ! [Flickr]

Jeremy Quinn: Aaaaaaaaah ! [Flickr]

Jeremy Quinn: Ooooooooh ! [Flickr]

Gianugo Rabellino: Time for some news: BPmo is on his way

The Apache Way: The Apache Way - Openness

Openness

What it means

Matt Raible: Happy Birthday Abbie!

Howard M. Lewis Ship: Tapestry 5: Java Power, Scripting Ease (ApacheCon 2009)

Sam Ruby: Web3D

Stephane Bailliez: Ubuntu 9.10 Server 64 bits in VMWare 7

Ben Laurie: Another Protocol Bites The Dust

Edward J. Yoon: Subversion Submitted to Become a Project at The Apache Software Foundation

Matt Raible: Testing GWT Libraries with Selenium and Maven

Assaf Arkin: Necktie: dress to impress

How Necktie Happened

Necktie In 15 Seconds

Tasks 101

Role play

Why Necktie, why not …?

Rich Bowen: Happy 10th Birthday Apache

Yoav Shapira: Boston Frisbee Halloween extravaganza!

Carlos Sanchez: Continuum-ruby

Example

Justin Mason: Links for 2009-11-04

Mads Toftum: Autumn has arrived

Luciano Resende: ApacheCon 2009 Session : SCA, Java EE, Spring, Web 2.0 and Cloud Come Together - Service assembly with Apache Tuscany SCA

Mads Toftum: Recipes: Sottofiletto di Manzo al Pepe Verde and Pere al Vino Rosso

Recipe: Sottofiletto di Manzo al Pepe Verde

Pere al Vino Rosso

Luciano Resende: Subversion is being proposed as an Apache Incubator project

Jan Materne: Getting the Samsung CLX 2160 MFC work under Windows 7

Sander Temme: ApacheCon US 2009 PGP Keysigning

Aidan Skinner: Litl launches!

Steve Loughran: rollback

Sam Ruby: SubVersion → ASF

Rich Bowen: ApacheCon US 2009, days 1 and 2

Sam Ruby: Introduction to Decentralized Extensibility

Chris Pepper: Mac OS X 10.6.1: Screen Sharing 64-bit bug

Screen Sharing to Linux vncserver fails in 64-bit

Aaron and Jenny Farr: I quit

Adrian Sutton: Conversion for the Web

Stephane Bailliez: Websites I Find Useful

Jacopo Cappellato: HotWax Media is Gold Sponsor at ApacheCon US 2009

Claus Ibsen: Getting started with Apache Camel webinar part 2

Bryan Pendleton: Coders at Work: Brad Fitzpatrick

Yoav Shapira: Book review: Orbiting the Giant Hairball

Yoav Shapira: Wine review: 2007 Crochet Sancerre

Jay D. McHugh: Goin back to Cali...

Justin Mason: Links for 2009-11-03

Nick Kew: Revisiting Apache 2.0 proxy

J. Chris Anderson: How CouchDB Treats the Disks

Apache Wicket Community News: London Wicket Event November 21st

Sander Temme: My ApacheCon US 2009 Wishlist

Sagara Gunathunga: ASF Big Feather Birthday Bash at Aeturnum

Bryan Pendleton: JUnit, tearDown, and uncaught exceptions

Bertrand Delacretaz: JCR in 15 minutes

Screen Sharing to Linux `vncserver` fails in 64-bit