JavaOne brain dump

Probably the best talk i attended was the BOF on Hudson presented by Kohsuke. It was an amusing history of creating a successful grassroots project, scavenging and building hardware, and encouraging others to join the project. IMHO such a talk would make a great technical session.

JavaFX (p.k.a F3) looks kind of interesting. It is very SVG like but has a nice language feature to avoid the spaghetti  that results from using the listener pattern. However, what does this mean for being on the Web? Web sites that are created in flash are essentially devoid of information that can be grokked by a search engine, or bookmarked, or annotated etc. A combination of HTML and SVG retains visible links while still giving a flash like-experience if required.

The talk on the Google checkout API was a bit disappointing. I was hoping for more detailed information on the protocol to see if it was a RESTful design or not (i guess i will 'check' it out in more detail) and how it was implemented for scalability. A member of the audience asked a poignant question about if/when Google will provide a feature so that checkout does not redirect to the Google site, because they loose customers as they do not go back to the original site. They will not and for good reason (think advertising revenue).

Mark Hapner's talk on "Wire"-Centric integration was interesting. It is worth listening very carefully to what Mark says as there is a lot of good advice compressed into his sentences. The focus of the talk was very much on the developer of a service being aware of the implications of what is going on the wire (which is rather different to our current programming models) and being aware that simplicity is important for a successful service to be consumed (in ways that the developer of the service may never expect). IMHO what goes on the wire is very important but even more important is how that which is on the wire is identified (which was only discussed in passing). If there is a uniform way of identifying what is on the wire, a uniform way of accessing what is on the wire, and an agreed convention for transitioning from states (correlations) then what do we have :-)

Jerome Dochez gave an interesting talk on the modular architecture of Glassfish V3. In combination with talk on comparing EE 5, Ruby on Rails and Grails by Tom Daly and Damien Cooke it made it clear to me that Glassfish V3 is well positioned to become a rock solid container for hosting Web applications, whatever the framework or language. With the likes of Ruby, Groovy and JavaScript languages running on the JVM it makes a lot of sense to reuse all that EE experience and infrastructure for managing and scaling to deploy JRuby on Rails, Grails, Phobos and EE applications.

I enjoyed Ludovic Champenois and Robert Chinnici's talk on Phobos. Phobos's sweet spot is being able to use Javascript on the service-side and client-side. The database demo was interesting and in debug mode was very dyanmic (Roberto mentioned in passing that it was possible to dynamically generate all the Javascript for the controllers and views without the developer even seeing it). I need investigate Phobos more closely. Maybe there is a nice integration point between the REST API and Phobos where a POJO matching an HTTP request is a controller and can be access as a bean by the view.

The talk i wanted to attend but never got around to? The one on DTrace by Adam Leventhal. Oh well... maybe next year. 

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

sandoz

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today