Notes from 16-Feb checkpoint meeting on Higgins Selector harmonization.
Attendees: Andy, Alexander, Jeesmon, Paul, Brian
Discussion Notes - the main short term focus is to prepare for the FC2 demo on 11-March
- The general wiki page with design details and general status points is located here: http://wiki.eclipse.org/Selector_Architecture_Harmonization
- Client side updates - Andy
- Have developed two skeletal card store providers. One is REST based and the other is SOAP based to connect to Azigo back-end I-Card Service. REST based one is set up to talk to backend or LICS to request list of cards, add cards, update card and authenticate using basic authentication.
- The DigitalMe based UI can talk REST to LICS and LICS could talk to service via existing soap.
- For this week, will focus on the GUI interface with LICS and wait for the REST support due later this week. Will work on the basics of get list of cards, card id and get cards based on unique id's. Will build up a few of these basic requests. There is a single method call 'getCardsAndCategories' that will get all information about the cards with this one call.
- As it becomes available, Andy will get share basic documentation so we can look at this for longer term connection to AIR selector at some point in the future.
- Server Side updates - Alexander
- Working on REST web binding to ICS. This REST capability will support user profile and basic p-card operations. The goal is to deploy these during this week in support of demo.
- Also created some new projects in Eclipse and will be submitted to svn. Alex will prepare some updated diagrams for review so we are clear on what the new projects are being added (e.g. some test components have been created).
- Will plan to use un/pw as basic authentication for requests.
- As a result of above discussion, the architecture diagram was updated as noted here: http://wiki.eclipse.org/Selector_Architecture_Harmonization#Synchronizing_Card_Store_.28Component_Set.29
We will continue to iterate via email over the course of this week and plan for another skype touch base meeting next Monday the 23-Feb at 11:00am ET.
regards...Brian
On Feb 4, 2009, at 10:28 PM, brian walker wrote: Notes from Higgins Selector Harmonization meeting
Attendees: Alexander, Andy H, Paul, Jeesmon, Brian
Discussion Notes: - Sent out open email to HIggins Dev team on Sunday 1-Feb to announce this project to wider audience.
- Open issues review - see the list of items here: http://wiki.eclipse.org/Selector_Architecture_Harmonization#Open_Issues
- Use of WebDAV - our assessment at this point is to not pursue WebDAV. The main reasons are it is not RESTful and there are issues with web-cache and proxy management (from W3C perspective). Does not appear to be significant advantages to make it worthwhile to pursue.
- Use Google protocol buffer - Would need to assess this for factors such as clean IPR, multiple implementations and strong documentation to help ensure broad support and adoption. Also discussed going with our own SOAP or RESTful protocol and where each would be more appropriate. There was general observation made of the places where SOAP and RESTful solutions are most appropriate: Often a RESTful approach is best where client is talking to sever via trusted connection and is lighter weight. SOAP on the other hand is appropriate where one needs long, possibly untrustworthy handoff to many server endpoints. However with SOAP need to verify integrity of message. Based on this general assessment, for the Higgins selector harmonization we will move forward with a RESTful based approach. Please voice fact based points if anyone feels this is not the correct approach.
- We will also pursue use of Jersy/JAXRS -
- What we need to demo for March FC2 meeting - We discussed the high level demo goals for the FC2 meeting in March:
- Show client side DigitalMe core (Andrew working this piece) talking to Higgins development BE being put together by Alexander.
- We will plan to be able to demo this on a Mac
- The basic workflow we would like to show includes: Prompt for un/pw for log-in to selector, show an existing set of i-cards. Demo log-in to an example RP site. Show creating of a new pcard in DigitalMe and then demo being able to access these same cards via another selector (e.g. iPhone).
- Discussion of general selector interface to LICS:
- In the long run (1yr+) would like to have AIR UI running on DigitalMe/LICS core client side code.
- The general interface model we are returning to is to have a pluggable UI that communicates LICS via xmlrpc (or some other) calls. Would like the LICS have same interface as server-side ICS over the period of a couple of years to fully harmonize these components.
- The design intent is to preserve stateless LICS (RESTful). We would however need to look at making sure we are not passing long term credentials across the wire. Eventually should be able to have LICS run on a remote server as well on client.
- We identified an OPEN ISSUE that needs to be worked through: Need to have verification/authentication between selector and browser plug-in to LICS. This needs to consider factor in design of LICS.
- General development status
- Andy - organizing the Higgins and DigitalMe code into necessary components to support this project. Trying to make sure we are not making local copies into these sub-projects so the bug fixes will benefit all components. Will work on making a new page to capture Andy's new solution organization.
- Alex - Continue to refine the design points for cardsynch protocol. Will have another update to wiki page next week for review. Please see this page to review the latest: http://wiki.eclipse.org/CardSync_Protocol
Please let me know if you would like to be included in the next selector harmonization meeting.
regards...Brian Brian Walker =brian.walker VP of Engineering Parity Communications Inc cell: 781-801-0254
<ATT00001.c>
Brian Walker =brian.walker VP of Engineering Parity Communications Inc cell: 781-801-0254
|
