OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cgmo-webcgm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [cgmo-webcgm] getWebCGMViewerVersion


I would lean slightly to option B because I feel that an application
may be more concerned with the viewer name than the version.  My
only concern is do we want to restrict the version to a "number".
It is important to be able to be able to sort the versions.  But 
what about minor version rolls 3.2 .vs. 3.2.2?


--
Stuart Galt
SGML Resource Group
stuart.a.galt@boeing.com
(206) 544-9925 

-----Original Message-----
From: Benoit Bezaire [mailto:benoit@itedo.com] 
Sent: Monday, May 16, 2005 3:09 PM
To: cgmo-webcgm@lists.oasis-open.org
Subject: [cgmo-webcgm] getWebCGMViewerVersion


I took an action at the last telecon for making a proposal on defining a
method for identifying the current plugin. So here it is... I think we
have two options, 1 method or 2 methods:

Proposal A:
string getWebCGMViewerVersion()
 returns a string identifying the User Agent being used (ex: Lofton's
viewer; 1.0)

pros: one call.
cons: no real control on string content.


Proposal B:

string getAppName()
  returns the application name (ex: Lofton's viewer).

number getAppVersion()
  returns the application version number (ex: 1.0)

pros: spec is clear on expected return values.
cons: two calls instead of one.

Thoughts?

-- 
 Benoit                 mailto:benoit@itedo.com



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]