Re: About proper use of mantissa.sharing...

On Sun, Apr 6, 2008 at 11:49 PM,  <[email protected]> wrote:

>  The key problem with this is: don't render items in the app store.  You
> should try to never use store.parent in your application code.  The few
> places you really do need to use it, you should be aware that this is
> because of a missing feature in the infrastructure; in a few months, there
> should be literally zero places that these sorts of links are required.
>
>  One question: why an app store and not the user store?  I don't understand
> your use case at all, so I can't really offer a solution (or even point to
> all of the relevant open tickets: this is a sticky area of the
> infrastructure that we are actively cleaning up).
>

The reason for putting things in the app store is if the object
doesn't really belong to any user... for example, a wiki article (for
a wiki that is purely public). I may be misunderstanding what should
be going on here, and it might make more sense to still have these in
a user store... I would appreciate some input on this. If it does in
fact belong in the app store, does this legitimize the rendering of
app items in user stores?

>  I believe you're also going to need this:
> http://divmod.org/trac/ticket/2554 which I need to review.  This would allow
> you to use items in app stores according to normal sharing rules; right now
> they have kind of wonky requirements.
>
>  Once those tickets are resolved, you can do something like what I describe
> below.  Hopefully you can either help us resolve them somehow or do
> something that is similar in spirit to this summary until they're done.
>
I will see what I can do!

>  First of all, don't create any items in a renderer.  Ever.  Why would you
> do that?  Don't.  This has nothing to do with app stores or user stores;
> this is basic model/view separation stuff.
>
Yes, my example was very bad in this respect.

>  However, think about who owns the data; if you billed for every bit in your
> system, are you billing it to the application, or is it owned by a
> particular user?  Examples of data billed to a user: their blog posts, their
> emails, status updates, inventory records, etc.  Billed to the application:
> indexes, data that is placed on the front page of a public site,
> aggregations (top ten lists, etc).  Most of the time, the link actually goes
> the other way: items in an app store ought to be shallow copies, and
> pointers to, relevant information owned by a particular user.  For example,
> keep in mind that users don't need to be simply end- users either, you could
> make a user like "north american continent" if it's convenient.

Hmm, I have trouble seeing how a user like "north american continent"
makes sense... would it only serve as a sort of store space for data?
What does this user mean with respect to the other potential
applications on your site?

-- 
Alex