October 2009 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Thu Oct 1 15:40:09 CDT 2009
Ending: Thu Oct 29 11:52:50 CDT 2009
Messages: 215

• [occi-wg] HTML5 at Last Call (and what this has to do with OCCI)   Andrew de Andrade
• [occi-wg] Issue 13   Michael Behrens
• [occi-wg] Issue 13   Michael Behrens
• [occi-wg] Issue 13   Michael Behrens
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Michael Behrens
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Michael Behrens
• [occi-wg] confusion about status of link / headers   Michael Behrens
• [occi-wg] Test suite for OCCI   Michael Behrens
• [occi-wg] What Language Does the Cloud Speak, Now and In the Future?   Michael Behrens
• [occi-wg] Horizontal & vertical scalability in the cloud   Randy Bias
• [occi-wg] Horizontal & vertical scalability in the cloud   Randy Bias
• [occi-wg] confusion about status of link / headers   Tim Bray
• [occi-wg] confusion about status of link / headers   Tim Bray
• [occi-wg] confusion about status of link / headers   Tim Bray
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Bill Burke
• [occi-wg] New http section of the document   Mark A. Carlson
• [occi-wg] confusion about status of link / headers   Mark A. Carlson
• [occi-wg] Great developer-focused use cases for Infrastructure APIs   Adrian Cole
• [occi-wg] Reminder first OCCI session starts in 2 hours   Adrian Cole
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] confusion about status of link / headers   Adrian Cole
• [occi-wg] name-based access to resources   Adrian Cole
• [occi-wg] name-based access to resources   Adrian Cole
• [occi-wg] name-based access to resources   Adrian Cole
• [occi-wg] Support Documentation for Today's Meeting   Richard Davies
• [occi-wg] Support Documentation for Today's Meeting   Richard Davies
• [occi-wg] help needed & this weeks OCCI concall   Edmonds, AndrewX
• [occi-wg] confusion about status of link / headers   Edmonds, AndrewX
• [occi-wg] confusion about status of link / headers   Edmonds, AndrewX
• [occi-wg] confusion about status of link / headers   Edmonds, AndrewX
• [occi-wg] can't make concall today...   Edmonds, AndrewX
• [occi-wg] EMC Atmos Online Compute Service REST API   Wes Felter
• [occi-wg] Test suite for OCCI   Patrick Grant
• [occi-wg] Save the dates: 2-3.12.2009 IGT2009 – The World Summit of Cloud Computing   IGT
• [occi-wg] The latest occi document checkin was not merged, other changes were discarded.   Sam Johnston
• [occi-wg] New http section of the document   Sam Johnston
• [occi-wg] What happened to occi-infrastructure ?   Sam Johnston
• [occi-wg] EMC Atmos Online Compute Service REST API   Sam Johnston
• [occi-wg] Issue 4   Sam Johnston
• [occi-wg] Foreign markup and extensibility   Sam Johnston
• [occi-wg] Issue 13   Sam Johnston
• [occi-wg] Reminder first OCCI session starts in 2 hours   Sam Johnston
• [occi-wg] Sam Johnston - OCCI Presentation   Sam Johnston
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Sam Johnston
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Sam Johnston
• [occi-wg] Fwd: [rest-discuss] hateoas - draft #1   Sam Johnston
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Sam Johnston
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Sam Johnston
• [occi-wg] Modeling proposal for ReST/Cloud based commands.   Sam Johnston
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Sam Johnston
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Sam Johnston
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Sam Johnston
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] GridForge down again?   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] GridForge down again?   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] About deleting a resource and what to return   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] Link relations (was Re: confusion about status of link / headers)   Sam Johnston
• [occi-wg] name-based access to resources   Sam Johnston
• [occi-wg] confusion about status of link / headers   Sam Johnston
• [occi-wg] William Vambenepe: Missing out on the OCCI fun   Sam Johnston
• [occi-wg] Some (thankyou) thoughts from OGF27   Sam Johnston
• [occi-wg] William Vambenepe: Missing out on the OCCI fun   Sam Johnston
• [occi-wg] Supporting standard formats   Sam Johnston
• [occi-wg] Addressing the Challenge of Cloud-Computing Interoperability   Sam Johnston
• [occi-wg] A few important clarifications...   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] Test suite for OCCI   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] OCCI JavaScript libarary   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] Test suite for OCCI   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] Fwd: OCCI JavaScript libarary   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] Horizontal & vertical scalability in the cloud   Sam Johnston
• [occi-wg] What Language Does the Cloud Speak, Now and In the Future?   Sam Johnston
• [occi-wg] Fwd: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard   Sam Johnston
• [occi-wg] HTML5 at Last Call (and what this has to do with OCCI)   Sam Johnston
• [occi-wg] Terminology: containers, workloads, templates and instances   Sam Johnston
• [occi-wg] Terminology: containers, workloads, templates and instances   Sam Johnston
• [occi-wg] OCCI JavaScript libarary   Sam Johnston
• [occi-wg] OCCI JavaScript libarary   Sam Johnston
• [occi-wg] OCCI JavaScript libarary   Sam Johnston
• [occi-wg] Weekly conf call: consensus on the formats issue   Sam Johnston
• [occi-wg] please read: OCCI F2F meeting   Thilo Kielmann
• [occi-wg] please read: OCCI F2F meeting   Thilo Kielmann
• [occi-wg] help needed & this weeks OCCI concall   Gary Mazz
• [occi-wg] Fwd: Support Documentation for Today's Meeting   Gary Mazz
• [occi-wg] What happened to occi-infrastructure ?   Gary Mazz
• [occi-wg] Changes to the occi-infrastructure.xml   Gary Mazz
• [occi-wg] The latest occi document checkin was not merged, other changes were discarded.   Gary Mazz
• [occi-wg] New http section of the document   Gary Mazz
• [occi-wg] occi-infrastructure.xml merged   Gary Mazz
• [occi-wg] Consolidated list of editorial changes from issues list   Gary Mazz
• [occi-wg] Issue 13   Gary Mazz
• [occi-wg] Foreign markup and extensibility   Gary Mazz
• [occi-wg] Issue 13   Gary Mazz
• [occi-wg] Issue 13   Gary Mazz
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Gary Mazz
• [occi-wg] Fwd: New Version Notification - draft-dusseault-http-patch-15.txt   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] GridForge down again?   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] confusion about status of link / headers   Gary Mazz
• [occi-wg] name-based access to resources   Gary Mazz
• [occi-wg] name-based access to resources   Gary Mazz
• [occi-wg] still can't get to concall   Gary Mazz
• [occi-wg] Horizontal & vertical scalability in the cloud   Gary Mazz
• [occi-wg] Test suite for OCCI   Gary Mazz
• [occi-wg] Horizontal & vertical scalability in the cloud   Gary Mazz
• [occi-wg] Test suite for OCCI   Gary Mazz
• [occi-wg] Horizontal & vertical scalability in the cloud   Gary Mazz
• [occi-wg] OCCI JavaScript libarary   Gary Mazz
• [occi-wg] Weekly conf call: consensus on the formats issue   Gary Mazz
• [occi-wg] New http section of the document   Andre Merzky
• [occi-wg] GridForge down?   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] GridForge down again?   Andre Merzky
• [occi-wg] GridForge down again?   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] confusion about status of link / headers   Andre Merzky
• [occi-wg] Moving Forward   Andre Merzky
• [occi-wg] OCCI JavaScript libarary   Andre Merzky
• [occi-wg] OCCI JavaScript libarary   Andre Merzky
• [occi-wg] please read: OCCI F2F meeting   Andre Merzky
• [occi-wg] please read: OCCI F2F meeting   Andre Merzky
• [occi-wg] help needed & this weeks OCCI concall   Thijs Metsch
• [occi-wg] Fwd: [wg-all] New documents in public comment   Thijs Metsch
• [occi-wg] help needed & this weeks OCCI concall   Thijs Metsch
• [occi-wg] Reminder: OCCI weekls concall today - 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST   Thijs Metsch
• [occi-wg] Consolidated list of editorial changes from issues list   Thijs Metsch
• [occi-wg] fixed issue 2, 10, 14...   Thijs Metsch
• [occi-wg] Issue 4   Thijs Metsch
• [occi-wg] OCCI Sessions at OGF27   Thijs Metsch
• [occi-wg] Reminder first OCCI session starts in 2 hours   Thijs Metsch
• [occi-wg] second session   Thijs Metsch
• [occi-wg] feedback from OGF   Thijs Metsch
• [occi-wg] Short statement about consensus reaching etc.   Thijs Metsch
• [occi-wg] Some (thankyou) thoughts from OGF27   Thijs Metsch
• [occi-wg] can't make concall today...   Thijs Metsch
• [occi-wg] Reminder: concall today: 4pm CET,   Thijs Metsch
• [occi-wg] please read: OCCI F2F meeting   Thijs Metsch
• [occi-wg] please read: OCCI F2F meeting   Thijs Metsch
• [occi-wg] please read: OCCI F2F meeting   Michele Orrù
• [occi-wg] confusion about status of link / headers   Alexander Papaspyrou
• [occi-wg] Horizontal & vertical scalability in the cloud   Alexander Papaspyrou
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] confusion about status of link / headers   Alexis Richardson
• [occi-wg] Supporting standard formats   Alexis Richardson
• [occi-wg] Terminology: containers, workloads, templates and instances   Strong, Paul
• [occi-wg] Fwd: Support Documentation for Today's Meeting   Tino Vazquez
• [occi-wg] Support Documentation for Today's Meeting   Tino Vazquez
• [occi-wg] About deleting a resource and what to return   Tino Vazquez
• [occi-wg] About deleting a resource and what to return   Tino Vazquez
• [occi-wg] help needed & this weeks OCCI concall   behrens
• [occi-wg] help needed & this weeks OCCI concall   behrens
• [occi-wg] Issue 4   behrens
• [occi-wg] OCCI JavaScript libarary   eprparadocs at gmail.com
• [occi-wg] OCCI JavaScript libarary   eprparadocs at gmail.com
• [occi-wg] Great developer-focused use cases for Infrastructure APIs   shlomo.swidler at gmail.com
• [occi-wg] GridForge down?   shlomo.swidler at gmail.com
• [occi-wg] confusion about status of link / headers   gary mazzaferro
• [occi-wg] confusion about status of link / headers   gary mazzaferro

Last message date: Thu Oct 29 11:52:50 CDT 2009
Archived on: Tue Aug 24 03:59:00 CDT 2010

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...