Skip to main content

Home/ Diigo Community/ containers, contents, domains, objects, views, layers, ACLs and other guesses
Graham Perrin

containers, contents, domains, objects, views, layers, ACLs and other guesses - 30 views

groups.diigo.com www.digo.com list bookmark ACL UI object guess gpd4

started by Graham Perrin on 17 Jan 09
  • Graham Perrin
     
    Scott Allam wrote:

    > I look at everything as containers and contents …

    > For example: Groups are containers. So are lists. When a group or
    > a list is private, any bookmark placed inside should default to
    > the attributes of its parent. So in that regard, I agree with
    > Graham (I think I am understanding his position on this matter). …

    I have two basic assumptions:

    1) about.diigo.com , groups.diigo.com , message.diigo.com , www.diigo.com
    and other diigo.com ¿subdomains? do not necessarily share the
    same technologies/qualities

    2) bookmarks, annotations and tags are objects.

    If the objects assumption is true: I don't know whether any/all such objects are contained within a database, or discrete in file systems.

    ACLs (access control lists)? I have no idea.

    My senses of acquisition and ineritance (not the same thing) are slanted by my very vague familiarity with ZODB. I occasionally glance at resources such as
    http://plone.org/documentation/glossary/acquisition
    http://wiki.zope.org/zope2/Acquisition
    http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/Acquisition.stx but my use (of Plone) doesn't require me to actually *know* such things.

    The slants and gaps in knowledge mean that my guesses could be completely wrong, but I do allow the guesses to stall me (believe it or not!) on a number of topics.

    Closing thoughts:

    * I do not encourage anyone else to share my guesses

    * I do not expect Diigo to confirm or correct any of what's above
    (APIs should be more interesting) (other quiet priorities are appreciated)

    * rewinding to a November expression: to avoid disappointment,
    at least for myself, I set no perceptions in stone.

    Incidentally, I do not think of a list as a container ;)
  • anonymous
     
    In general I was using the conceptual terms of containers and contents as generic expressions, given that this is a public Diigo group with many non-developers present. So groups and lists would be a data structure, which holds a set of objects if you will, most likely held in a database, but who is to say. My use of the word inheritance, therefore, was not meant literally as is used in OOP. That too was meant generically that bookmarks, annotations and other associated objects would be like their parents, i.e. private things be hidden from public view. How that is achieved would be up to the Diigo developers and their current architecture.

    Just clarifying my position on the matter.

    Grant said:
    > I do allow the guesses to stall me (believe it or not!) on a number of topics.

    LOL, nor me :-)

To Top

Start a New Topic » « Back to the Diigo Community group