meta use

[William Reade]

Hi Mike

Without some distinction between provider and requirer, there's no way to
tell which charms can reasonably be connected to one another. If a node.js
charm and a django charm both declare a postgres interface alone, it would
appear that they could be reasonably connected to one another... but that
doesn't make any sense. By making them both *require* postgres, and making
the postgresql charm *provide* it, it's immediately clear (both to humans
and to machines) that node<->postgresql makes sense, and
django<->postgresql makes sense, but node<->django doesn't.

Does that answer your question?

Cheers
William


On Fri, Sep 6, 2013 at 1:24 AM, Mike Sam <mikesam460 at gmail.com> wrote:

> How does juju use the extra information inside meta file about knowing who
> is the requirer and who is the provider in a relationship? I mean if each
> side process their join and changed independently and anyone can call
> relation-set, why would juju care to know who is providing and who is
> requiring?
>
>
>
>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130906/660f7fb6/attachment.html>