This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqNF11?selectedTab=associations at Sun, 06 Nov 2022 11:28:19 GMT SourceForge : View Wiki Page: ReqNF11

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: pgi-wg     Wiki > ReqNF11 > View Wiki Page
wiki2256: ReqNF11

Req. Nb ID Description Source Areas Dependencies Status Date
NF11 153 Backwards compatibility (on-the-wire) not a precise requirements, conceptual backward compatibility a must - new portType - new compilation anyway but general concept should be kept. NSF 08-571 Reuse Specs Conflicts with NF9 Open (unclear) 2010-04-29

Andrew Grimshaw on 2010-03-20

  • Propose requirement with title  'Backwards compatibility (on-the-wire) not a precise requirements, conceptual backward compatibility a must - new portType - new compilation anyway but general concept should be kept.'

Etienne Urbah's position on 2010-04-07

  • For clarity, I suggest to change the original title to
    'Execution Service MUST provide conceptual backward compatibility (perhaps requiring recompilation of client), even if it does NOT provide on-the-wire backward compatibility (which would avoid recompilation).  For example, specifications SHOULD NOT overload existing portTypes or operations, but keep them, remove only unused existing ones, and add new portTypes or operations when necessary'
  • Anyway, I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-27

  • Spreadsheet ID = 153

Amsterdam meeting on 2010-04-29

  • Open  (still unclear)
 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqNF11?selectedTab=associations at Sun, 06 Nov 2022 11:28:19 GMT