You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Anton Tagunov <at...@mail.cnt.ru> on 2003/05/16 08:51:35 UTC

Re[2]: [RT] Avalon Bundles/Distribution Units [LCD l10n wrt resource management API]

Hello, Developers!

Personally me, I've been dreaming for years about this kind of
functionality... ...so me too! :-))

PD> I don't see what relevence these points have wrt to a generic resource
PD> access API.

PD> Avalon is not a resource management API despite the hacks that have been added
PD> to it so why try to make it one?

Dunno for sure, but l10n seems to be a concern crosscutting almost
any kind of software, probably will be nice to have some support?

PD>                             ... what relevence does this have to the API?
PD> This is not an API question but a policy for usage and instantiation of a
PD> resource.

I)

  Maybe this can be handled DECLARATIVELY via a POLICY?

  Policy examples:

  - LCD
  - LCD, but JA should be supported by everyone - otherwise complain loudly
  - some other policy to complain loudly in some other case
  - MIXED (serve mixed locale content)

II)

  Semi-orthogonally to this the code that chooses the locale would
  benefit from knowing what locales are available (the policy can
  affect this: for LCD it would be the intersection, for MIXED -
  union).

  Dunno if such code should be normal component code (and then
  this info may be retrievable via a special API call) or
  special-purpose call-back code (bundle or partition scoped),
  and then such callback would receive the list via its method
  arguments)

BL> What I am proposing is that the bundles be able to *declare* what
BL> locales they support.  What to do with it from there on is up to
BL> the user of the API.  Whether it is verification, the LCD approach,
BL> or allowing the user to extend the bundle to include the new values,
BL> etc. that's fine.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org