An idea, maybe the solution (was Re: Continuing discussion of oaf ...)

[Martin Baulig <martin home-of-linux org>]

Hi guys,

just had an idea which may be the ideal solution for us.

Would it work if we do the following ?

1.) Require the UUID in the oafinfo files and when creating components
    (ie. in the component's factory).

2.) Namespace the OAFIID and use a format like

        OAFIID:<component-name>:<version-number>:<uuid-goes-here>

    where

        component-name - namespaced component name (not to confuse with
                the IDL name) such as:

                GNOME_eog_image_viewer

        version-number - optional version number such as

                1.0

        uuid-goes-here - the UUID

3.) In all oaf calls which activate an object (ie. in some application which
    wants to activate the component, not in the component itself), make every-
    thing after the colons optional, but let a trailing colon force an exact
    match.

    This means, for

        OAFIID:GNOME_eog_image_viewer:1.0:3ed29918-f636-43e4-8a0d-e140f608e58a

    the following would be equivalent

        OAFIID:GNOME_eog_image_viewer
        OAFIID:GNOME_eog_image_viewer:1.0
        OAFIID:GNOME_eog_image_viewer:1.0:3ed29918-f636-43e4-8a0d-e140f608e58a

    However, for

        OAFIID:GNOME_eog_image_viewer:3ed29918-f636-43e4-8a0d-e140f608e58a:1.0

    the following would work

        OAFIID:GNOME_eog_image_viewer
        OAFIID:GNOME_eog_image_viewer
        OAFIID:GNOME_eog_image_viewer:3ed29918-f636-43e4-8a0d-e140f608e58a

    but this would not since it'd require an exact match:

        OAFIID:GNOME_eog_image_viewer:3ed29918-f636-43e4-8a0d-e140f608e58a:

How does this sound ?

-- 
Martin Baulig
martin gnome org (private)
baulig suse de (work)