[Xen-cim] Rework of association providers

["Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>]

Jim -

I agree with the approach you suggest.  

As far as where to keep the common code, I have no strong feelings
either way, mostly because I can't see too many compelling arguments one
way or the other.  I suppose we need to clarify - does this code not
"belong" in cmputil ?  And if we put this code in a separate file, do we
foresee many other structures which would go in their own separate files
and thus create a pattern which might get out of hand?  Ultimately, I
would just go with whatever is easiest to maintain down the road.

Luke

-----Original Message-----
From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-cim-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
xen-cim-request@xxxxxxxxxxxxxxxxxxx
Sent: Monday, October 23, 2006 1:31 PM
To: xen-cim@xxxxxxxxxxxxxxxxxxx
Subject: Xen-cim Digest, Vol 9, Issue 5

Send Xen-cim mailing list submissions to
        xen-cim@xxxxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim
or, via email, send a message with subject or body 'help' to
        xen-cim-request@xxxxxxxxxxxxxxxxxxx

You can reach the person managing the list at
        xen-cim-owner@xxxxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Xen-cim digest..."


Today's Topics:

   1. [RFC] Rework of association providers (Jim Fehlig)


----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Oct 2006 11:29:51 -0600
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: [Xen-cim] [RFC] Rework of association providers
To: xen-cim@xxxxxxxxxxxxxxxxxxx
Message-ID: <453CFC0F.7010803@xxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Attached is a patch (applies cleanly to tip) for the association
abstraction work we have been discussing.  Only 2 associations
(Xen_CSElementSettingData and Xen_ProcessorPoolComponent) have been
ported to the new common code in cmpiutil.  I would like everyone to
agree to this new approach before porting the remaining association
providers.

The only issue I have with the patch at this point is whether to place
the common code (_CMPIGetTargetEndpoints and its related structures) in
cmpiutil or in a new file.  As you can see, it currently resides in
cmpiutil.[ch].

If there are no objections I will port the remaining association
providers and commit to the repository within a few days.

Thanks,
Jim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: assoc_rework.diff
Type: text/x-patch
Size: 66890 bytes
Desc: not available
Url :
http://lists.xensource.com/archives/html/xen-cim/attachments/20061023/6d
b44ba2/assoc_rework.bin

------------------------------

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim


End of Xen-cim Digest, Vol 9, Issue 5
*************************************

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim