Hi Koos, The reason of the separation between the Gadget Store implementation in the Shindig bundle and the Gadgement management REST service in a separate gadget management bundle had something to do with circular dependencies. I do not remember exactly what the problem was at the time, but I remember running into a circular dependency issue between the shindig, Cassandra and gadget bundles. See revision 129/AMDATU-56. However, in the current situation I agree that there seems to be no reason for the separation of gadget management service and gadget store (other than hiding Cassandra packages).
Regards, Ivo From: amdatu-users-bounces at amdatu.org [mailto:[email protected]] On Behalf Of Koos Gadellaa Sent: vrijdag 22 oktober 2010 10:15 To: amdatu-users at amdatu.org Subject: [Amdatu-users] Gadgetmanagement interface Hello, I'm wondering what the idea is behind the Gadgemanagement interface. It's essentially hiding the gadgetstore interface. However, the gadgetstore interface should in itself already hide all the implementation details of the gadget-storage. As is, the gadgetstore still exposes the use of Cassandra (which isn't proper, but is an other issue alltogether) and the gadgetmanager then hides this detail. I can imagine using the gadgetmanager to hide the gadgetstore (it would be the layer on which I would create the authorization for gadget-access, for example), but I'm not sure that is what the interface is for, actually. Kind regards, Koos Gadellaa | Software Engineer +31 6 317 658 01 My world is: ever expanding Luminis KIS B.V. Prins Willem Alexanderlaan 715 7311 ST Apeldoorn +31 88 586 46 25 http://kis.luminis.eu http://www.luminis.eu KvK (CoC) 09 14 31 09 BTW (VAT) NL8135.18.556.B.01 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.amdatu.org/pipermail/amdatu-users/attachments/20101022/231d566f/attachment.html
