finally scribed down some of my recent javaws optimization lessons learned experiences. in short, javaws totally rocks!

all but one of the number of issues i had w/ javaws over time were resovlvable via either moving to an more informative http server or tuning and annotating the jnlp descriptor files and the one issue that remains is a known and non-critical bug that is fixed in follow on releases.

javaws ... do it!

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Crystal Method/Community Service/Kalifornia

our second child was born last thursday, on the autumn equinox. while tammy and i have had a nice girls name picked out for literally years, the name just didn't seem to fit. being the first day of autumn and all, well, long story short, we chose the name "autumn marie todd." autumn is meaningful and somewhat unique and marie is my mother's and sister's middle name, that also goes along nicely with a first name of autumn.

i've posted some fresh-off-the-press pictures at our dot mac site.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: sounds of a newborn

one of my first ah-ha moments w/ jxta was when, for me at least, i envisioned it being, at it's lowest level, a socket. a kick a$$ socket, but a socket none the less. a socket that slurps up late binding and constantly changing addresses of varying protocols w/ ease. of course, there is more to jxta but for me, it was the socket perspective that intrigued me the most.

now, sockets are fine an all, w/ jxta socket being the tastiest of all, but it is what you do w/ said socket that matters. having worked on tomcat in the day (ahhhhh, good times), built a number of ecom systems (i *hate* the letter e as a result), and an interesting application at a startup (shudder) it's pretty obvious that http is, for the most part, fine. various protocols are stacked on http which are subject of debate, but http is, well, simple, and simple is good. can i get an amen!

w/ that as backing context and having an itch that has needed scratching for 2+ years now, and having a very real need to simply the $%^@ out of a current gig i opted to lay down some code that takes my tomcat experience and binds it squarely over the jxta socket keeping in mind all the while tha ease of use is paramont ... as i'm going to use this stuff myself. i've been talking about this for awhile now but talk is, well, cheap.

so, what did i end up with? here's the skinny. there is a server and a client component, probably more approriately noted as requester and responder moving forward in a jxta context as "this ain't your father's server."

here's what the server looks like:

  // xxx: a most excellent 1.5'ism
  URL.setURLStreamHandlerFactory(new JxtaURLStreamHandlerFactory());
  // xxx: server
  HttpServer s = new HttpServer(this.npg);

  s.addPeerlet("foo", "net.jxta.myjxta.dialog.http.RestPeerlet");
  s.start();

the basic idea is that one can start up a server (listener) socket and accept inbound connections. a series of "peerlets" can be registered, not entirely unlike a servlet, that will be selected as the connection handler delegate based on some regex mojo as specified by the key, a "webapp context" in servlet parlance. that's about it.

now, this is just a prototype as this point in time but, again, taking my past experience into account (mom taught me well, learn from life's lessons and be nice to people) here's what a peerlet looks like today (read hell'a simple):

import net.jxta.myjxta.dialog.http.Message;
import net.jxta.myjxta.dialog.http.Peerlet;

public class RestPeerlet
implements Peerlet {

  // xxx: pong
  public Message process(Message req) {
    Message m = new Message("pong");

    m.setHeader(Constants.CONTENT_LENGTH, String.valueOf(0));

    return m;
  }
}

now, the client side is where the fun starts to happen. well, it's all fun to be honest, but this is where my juices really start to flow. here's the basisc:

  URI u = null;

  // xxx: put this stuff in a factory of some sort bruth'a
  // xxx: in the real world teh pipe adv will be inferred from some other means
  try {
      String p = s.getPipeAdvertisement().getPipeID().toString();
      int c = p.lastIndexOf(COLON);

      u = new URI(JxtaURLStreamHandlerFactory.PROTOCOL +
          URI_DELIMITER + p.substring(p.lastIndexOf(COLON) + 1) + "/ping");
   } catch (URISyntaxException use) {
       use.printStackTrace();
   }

   System.out.println("u: " + u);

   // xxx: dispatch a request
   if (u != null) {
     Rester r = new Rester(u);
     Message req = new Message("ping");
     System.out.println("request: " + req);
     Message rsp = r.dispatch(req);
     System.out.println("response: " + rsp);
   } 

basically, given a uri with a specified protocol, in this case "p2pp," we can now use java-only classes to connect to the server and open input and output streams. in my case, i have a little rest engine baked into the mix which simply shuttle mime messages across the wire. which is precicely what i need right now, no, wait, i needed that like 2 years back. since my folding space-time continuum device is presently in for repairs i only have the present ... the result can be summarise as "meerkat," tomcat's fleet footed sibling. i'll expand on this more in following thread. till then, here's a joyous run:

execute:
    [java] connect
    [java] u: p2pp://uuid-5961626164616261[...]FAB41254E3268B04/ping
    [java] request: resource: /ping
    [java] content: null
    [java] response: resource: /pong
    [java] header[Content-Length]: 0
    [java] content: null 

not perfect but if one conciders how simple it was to get to this point it, well, thrills the heck out of me. the "jxta url protocl handler" can back pretty much anything, as my deep thinking compadre bblfish and i have discussed, well, since our paths first crossed via bloged code sling'age. on top of meerkat we can project any number of flavorful content, of which foaf:rdf looks the most attractive. myjxta has already start to shuttle about rdf data so we have an app with which to readily test pilot these ideas further.

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death In Vegas/Death In Vegas/Days Go By

tbray has earned his jxta wings.

thing is, i suspect we can cut down the current jxta configuration class to 1/3 the size ... something like the following is what i'm aiming for:

import net.jxta.ext.config.AbstractConfigurator;
import net.jxta.ext.config.Configurator;
import net.jxta.exception.ConfiguratorException;

public class MyConfigurator
extends AbstractConfigurator {
 public PlatformConfig createPlatformConfig(Configurator configurator)
 throws ConfiguratorException {
   configurator.setName("foo");
   configurator.setSecurity("bar", "bop");

   return configurator.getPlatformConfig();
 }
}

but i want to add the following:

• a main method
• instantiate the jxta platform

tim's got a piece of real-world code, as mentioned in his blog, that i'd like to start with, opting to take a small piece per blog and itteratively refactoring the code down the the bare essentials and no more. i suspect the outcome will be significanly application agnostic and perhaps the little thread we spin along the way will be enlightening. i promise, no holds barred with regards to diamonds in the rough, best practices and pitfalls.

tim ... your serve. can you post the code at which point to which i will reference it making subtle tweaks along the way.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Crystal Method/Community Service II/SpeedFreak

JXTA Technology Brings the Internet Back to It's Origin is really nice article that covers jxta context along with current and future state networks.

jxta is the net!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Crystal Method/Community Service II/The Crystal Methods Vs The Doors

i opted to update my home systems this weekend, ubuntu for my x86 box and tiger for my mac. in preperation, i bought a new firewire disk for backs and the like. the backup process took the most time, overall, but is well worth the time spent.

having received my *free* shipit cd's the same day that i unfortunately obtained a couple of cds after attending linux world i was chock full of install disks.

on the mac side of the desk i picked up a fresh tiger cd and opted to add ilife '05 to the mix.

with the backups safely offlined i dug in w/ the upgrades opting to give them a go concurrently, at least to start out. the ubuntu install process was quite fresh and in fact the overall time to get a login for each system was identical, noting that the requisite linux system pimp'age was still needed.

i'm really impressed with the ubuntu install process. the few prompts that were present we're extremely intuitive short the disk partitioning. even that process was a joy in comparison to some distributions. both of my internal disks were picked up. a swap partition was not called out which struck me as odd having *once* suffered a ill configured system with too little swap. i opted to specify /swap and moved on.

going with ubuntu is a coming home distribution for me as my first home linux system was debian dressed with enlightenment ... mmmmmm, great eye candy for sure.

this go around, though, gnome decked with my choice of swag jewelrey filled 'da bill.

once i got back to my day-to-day with the system i tried to su root only to be kicked to the curb. after frantically trying to remember the install prompts specifying a root password ... think think think ... and realizing that no such prompt was offered i opted to sudo, ahhh, joy! sudo is on by default and you can't, by default, su root. now that is just the way it should be and i was quite happy to not have to vi /etc/sudoers as a post-install process. this is not unlike osx, from an end users perspective. that being that (at least) one user is specified as a systems administrator.

the default programs were quite fresh, which was nice. i opted to pull down a new firefox and thunderbird and was really impressed with the new extensions and themes since i have last installed these tools. the "smooth scroll" extension is gold.

i was really happy to find the synaptic package manager, a sweet apt-get front end. what a joy that tool is too use. i really missed a tool like that when migrating off of debian a couple of years back. after adding some extended repositories to apt i stumbled upon bum, boot-up manager. this is a must have for service management. i also got a chance to install ethereal via a managed process which for reasons unknown was a pain in the a$$ on my former system. using ethereal for my day-to-day will be nice when i finally get a chance to try out the nice "ethereal jxta protocol analyzer" swag my colleague bondolo has cooked up.

i fought a bit with alsa to get my system utter sounds. i'm still grappling with nvidia driver support with the bar being a smooth playing game of bzflag with my son. i suspect this won't be too difficult to get in oder once i dig in.

i familiarized myself a bit with the x.org system, swapping my cntrl-and-caps keys and going big with 1280x1024 resolution. easy enough and ample resources abound.

all in all i'm quite impressed. great/free, literally free cd(s) & shipping, distribution. very smooth process. comprehensive forums, wikis, etc. the ubuntu community should be proud!

osx/tiger is great. dashboard is something my wife is sure to like. the updated iPhoto is something we had a great time with during the evening viewing old photos with new querying capabilities ... finding some we are going to photoshop a bit and and hang them on the wall.

the only downside to this systems upgrade weekend was that during the installs i opted to clean the mac keyboard. i was happy to find that it cleans up nicely, in comparison to the typical pc keyboard. the trouble was that i rushed a bit during the process and failed to ring out the paper towel thoroughly and ended up shorting out a couple of keys, namely escape, up-arrow and 4. i gave it another day to dry out to no avail so i chalked this one up to lessons learned and pennied up for a new keyboard.

all in all my home systems are singing away nicely.

i ended up updating my work system early on in the week and pretty much liked the results as well being greeted with a smooth gnome theme. i hope to get a desktop solaris 10 system under my mits soon.

i scored a couple of new cds this weekend as well. the crystal method, community service ii cd so rocks! this is a must have cd.

rock on!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Crystal Method/Community Service II/1979 (New Originals 1799 Remix)

given the build up to javaone '05 and netbeans day, then participating in the afore mentioned events in addition to jxta town hall followed by a most excellent and very non-virtual (read real) vacation i've offline for a spell ... and it felt really good :)

For NetBeans Day we presented "NetBeans/Collab:JXTA," which basically extends the NetBeans Collab module with true peering capabilities. More on this in the coming weeks.

Immediately following NetBeans day I re-presented the NetBeans/Collab:JXTA demo and provided MyJXTA updates, which now supports voice, video, a spiffed out UI, etc.

For JavaOne '05, which so totally rocked IMNSHO, we provided the second installment of the JXTA Hands On Lab (note: I'm not sure where the '05 HOL content is posted at this time). The JavaOne Pavillion was hopping and I met many new folks interested in JXTA along with a growing number of regulars.

Lastly, NetBEAMS, of which MyJXTA is a component, won a Duke Award under the "Community Category." This project was very rewarding in that the result, in this case, was a perfect blend of complimentary technologies to solve very real world (read wet and dirty) sensor telemetry management and collection. there is so much more we can do in this space. as such, i'm very much looking forward to "2.0" and again working with a great group of folks.

in aggregate. that's the opportunity. building solutions taking readily available and extremely enabling components to build out real world solutions ... in aggregate! good times.

over the vacation we worked on our long overdue bathroom remodelling project. given my father-in-law helped replumb recently we now have the tile layed (first timer for me) along with the swag radiant heating mats, walls and ceiling painted, floor and window trimmed and ceiling vent installed. next up we'll bring the claw foot tub into the room once i seal the tile and grout, calk the trim and fill and paint the trim nail holes. this project was supposed to be done before the arrival of our first child, how is 5yr old today. i'm betting i can beat the arrival of our second child, given a 5yr head start.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: New Order/Substance/The Beach

today's is trey's 5th birthday. oh man, does time fly.

we had a fun bday party this weekend, inviting trey's friends and family. tonight is the family party. just the 3 1/2 of us.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: trey/a very happy 5yr old

wow. that little one gig has surely blossomed. i'll be watching. i'm not surprised, not at all. sun rocks. i mean, literally rocks!

given that cell phones are the modern successor to cigarette lighters of old, a sea of individual beacons, shining in unison, i wonder, what next? what next? ponder. hmmmmmmmmm.

what if ... what if the phones pulsated in response to their environment, their surrounding, in response to one another. now, that would truly rock! but how? hmmmmmm ... <thinking-hat="winnie the pooh">think think think</thinking-hat> ... ahhhhahhhh, but of course. jxta is the unifying glue. the neon thread that binds the network fabric by bringing together disparate entities floating about in adhoq flotsam jetsam ether regions to spontaneously unite for a common cause, be it for art or for humanity. optimally for both.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: New Order/Substance/Blue Monday

wow. netbeams won a dukie award at this years java one. here's a nice netbeams one-pager for those that are new to the project.

the netbeam's application domain is both immense and important, potentially life critical in the big scheme of things. the ability to realiably collect, manipulate, compute, display and act upon realtime, real world, telemetry from around the world spanning aquatic and land based sensors. further, by applying jxta it will become possible to securely command-and-control such sensors from afar.

this is just the start and nothing but good things will result as continued innovative and out-of-the box thinking is applied to this and like applications. and jxta is at the heart of it all. securerly and pervassively connecting disparent data sett flowing across varying networks creating bi-directional and truly "peered" relationships.

potential next steps include leverage of the java me jxta platform, broader federation of aggregated sources of a jxta network, richer client-side interativity along with a healthy mix of authentication, quality controls and, lastly, broader deployments into like domains. all leveraging a cadre of existing and maturing communities, including at this time but not limitted to jxta se, myjxta, jxta me, jddac and others.

applications rock but the people behind it are what drives progress. without open minds and unabashed willingness to collaborate the best of ideas are merely fading conversations. the folks behind netbeams are top-shelf and thus netbeams is born and off to an incredible start.

i've truly had a great time working with a set of new faces along with some great sun colleagues, namely james liu, jim wright and tai-wei lin. these lads rocked. we came together in short order and managed already busy commitments and schedules to do our part and truly raise the bar. i very much look forward to working with these folks again pushing jxta into deeper and broader domains.

join the fun. get connected.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Underworld/Dirty Epic/Dirty Epic

i just posted relatively comprensive james' javaone '05 gigs entry. hope meet new and old faces this year.

i was up at moscone today shoring up the jxta hand s-on-lab. those folks are so cool to work with and the hol content is getting better and better all the time. comprehensive yet very consistent. amazing considering all the vary topics and the number of authors involved. one thing is for certian ... these people CARE.

i'm quite happy w/ the end result ...

today should be alot of fun as we'll demo, for the first time, some of the kick a$$ work that has been keeping me really busy as of late at both netbeans day and the jxta town hall. killer!

during javaone i'll be hanging in the jxta, netbeams/jddac and orchestrated collaboration pods along w/ tipping a few w/ my bsc compadres :)

lastly, thx to the help of my brother michael my mom is now running the latest myjxta as she was stuck on an older build that didn't readily recognize jnlp mods. we did a video chat as well, which is was *really* looking forward to but alas it didn't render on her side of the connection. hmmmmmmm. we're close. we'll get it nailed.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Crystal Method/Keep Hope Alive/Now Is The Time

me luvs da free beer! be there.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Coldplay/A Rush Of Blood To The Head/Clocks

summer time. graduations. commencement speeches. reflection.

my brother graduated recently so i attended one such ceremony first hand. then, after perusing my inbox and such, i ran across two other commencement speechs, both of which are, well, inspirational. given i'm now putting spit-shine on my java one demos, spinning coldplay in my ipod and having a really nice northern california day stare at me through the window, i thought i'd jot down some of these quotes that truly struck a chord with me and why i dig, i mean *really dig*, software engineering, specifically jxta and, more importantly, the opportunity jxta provides.

ok, software engineering. why? everyone rightfully so has their own personal answers to that question. for me, it is the social connection, with real people, that is growing deeper and broader all at once that is behind every line of code i scribe. this first dawned on me, i guess, when i joined sun in '92 helping to work out the kinks in software licensing. in working w/ real people and building systems that spanned the globe and strived to "stay invisible" i found it was the network of people and associated processes i enjoyed working through the most. getting the code to compile was secondary. this is also why i'm a huge fan of xp as well, more on that later. i then moved on to the "e" projects, as in eReg, eCommerce, etc. while i'm proud of what was done, i wish not to work on another project that starts with the letter "e" again. why? well, in a nutshell is was the people, the network, the process that became, candidly, muddled during those heady days. so, i moved on, to swag projects like tomcat, startups, blogging, etc. why? because of the "people," the dialogs, the conversations that were occuring with these technologies and again, the applications that were and are being dreamed up and the fact "real" people, my mom, get to use the derivative works and the discussions start over again, at a higher level, with context, real context. that's what it is all about. the intermittent compile cycles and such are just necessary milestones to the "dialog" that drives innovation.

these cummulative experiences and basic curiosities are what drove me to jxta, an extremely enabling piece of technology, jxta "is" the network, to which the potential and associated dialogs are vast and very real. often, i grab folks first impressions, as quoted, when they use myjxta and post them to the the wall of words. these are real quotes. real people. my wife. my mom. new friends. this is very real. this is "the why" i engineer. the cummulative results of a small group of folks that ask "why" and incrementally start out on the mission, tuning and adjusting along the way, is what it is all about. make it "real." continue to ask "why."

ok, with that backing context in mind, and back to the afore mentioned commencements, what inspires me, in a nutshell? time to swim through some inspirational thoughts.

first up, greg papadopoulos delivered the commencement address for irvine. i can't find a link to the address so i'll include a couple of excerpts within. i do hope those that published the address do not mind, but as i see it, this stuff needs to be shared. made my day anyways.

from greg's address the following stood out, profoundly so:

Wanna be a great engineer? Know your stuff, make things that are simple and elegant, and embrace criticism in order to make them even better. That's all there is to it. Easy, huh?
...
It won't be easy, and it takes most of us years to reach a point where criticism of our work doesn't feel like criticism of our selves, but I think the place to start is with the realization that you have a responsibility to other people.
...
But your responsibility is actually much broader than that, because engineering has the capacity to touch the day-to-day lives of more people than any other discipline I can think of.
...
but the only way you would get there is by thinking in terms of the social context.
...
Practice engineering in a social context.
...
You have a duty to make things simple, usable, secure, and safe.

there it is. simple. concise. real. my take. add a mix of humility and great social awareness and it all becomes, well, grounded. real.

back to xp a bit. one of xp's fundamentals is "collective code ownership." this is manifested quite simply, using words like "our, we, and us" vs "you and i." in practice, it works ... when people step back and, well, relax.

ok, the other commencement i noted. theme, "connect the dots," by one steve jobs. read it. really. now, go read it. don't worry, i'll wait here for you when you have finished.

what stood out for me? connect the dots. easier said then done but obvious in hindsight. translation: DO IT!

we're all collecting dots. it's the journey that matters, not the destion to which i'll add it's what you do with dots you collected on the journey that truly matters. share and share alike. share dots. see what happens. see what you learn in return. society will be the better for it ... and so will you.

love. passion. need ... and compromise. to quote:

You've got to find what you love. And that is as true for your work as it is for your lovers. Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven't found it yet, keep looking. Don't settle. As with all matters of the heart, you'll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don't settle.

don't settle. do not settle.

in the end, it all only matters so much. this isn't a bad thing at all and in fact this perspective, alone, keeps in check all the little distractions that flirt by from time to time. some distractions are good. some are, well, in steve's case, potentially cancerous.

keep distractions at bay. don't settle. ask why ... and do it!

i'll post some of my engineering contributions soon, given java one is nearly at our doorstep. the ensuing dialogs, the "what next" dialogs are what i'm looking forward to for code simply compiles. what we do with it, collectively, is what matters.

collaborate. community. societal context. share. don't be left out.

rock on!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Coldplay/A Rush Of Blood To The Head/A Rush Of Blood To The Head

i've been mondo busy as of late. that and i took a little famly vacation just recently. as such, i'm just now coming back up for air ... so i thought i'd start with a "soft" entry followed up by something a bit more hard-core on gonzo@java.net shortly.

first off, listening to the new nin cd with teeth. love the "beside you in time" track. a-maze-ing. i had trouble ripping this cd and another (underworld) via itunes so i ended up using grip on linux and importing into the rest of my 36Gb itunes store. end result, i have complete joy on my ipod now.

speaking of the mac, my 6 month old imac got a bit crispy last week, just after i showed my mom the ways of mac. 3 days later, weekend included, i have it back post a new power supply and mother board. i do not recall a time where another piece of equipment or furniture was so missed by all of us in the household. i'm not sure it is quite right to love a piece of plastic so universally. oh well, we're hooked to the osx way, happily so. i must say, apple care gets an a+ in my book.

my family was in town last week for my brother dave's "executive mba" graduation from santa clara university. way to go davey! i'm really impressed. the lad pulled of this 1.5 year program whilst working fulltime for 2/3 of it in a global job that called for him to effectively work 6 days a week. wow. the lad rocks.

unfortunately my dad wasn't able to make the trek. it would've been his first time visiting us siblings who opted for the california way. next time.

my mom and tom did visit though. for the whole week. so, post dave's gradutation festivities we had great dinners, nice chats, fun w/ the only grandson/nephew for miles around and spent a very relaxing day at carmel by the sea and point lobos, a place my mom and i visit pretty much every time she's out here. point lobos is one of my favorite places along the california coastline. the oregon and washington coastlines are amazing as well although the convenience of having point lobos "in my backyard" is indeed a unique treasure. anyways, great times had by all.

i'm not sure i kicked into "vacation mode" as readily as i should have ... or would have liked to. up till then, and including a bit of time during the vacation, i had been pretty busy on a couple of projects, both of which will see the ligth of day next week, at java one. man, should be fun. i'll blog more of details in a bit.

jxta.org is making some nice and very real splashes these days. better and bigger every day in every way. i'm looking forward to chatting w/ jxta compatriots at java one. it's very refreshing to see the wide variety of applications folks are going after using jxta as the network enabler.

k. first blog since diving back into "reality." not to bad me thinks. more detailed info in a bit.

rock on peeps!

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Nine Inch Nails/With Teeth/Beside You In Time

just reached a major milestone in a little project i've been hammering away at. feeling good. this one was mondo challanging. lots of moving parts. phewwwww.

tomorrow should prove to be an interesting day.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Led Zeppelin/How The West Was Won/Dazed And Confused