Received: by 10.101.134.33 with SMTP id l33mr1437566ann.3.1337175562480;
        Wed, 16 May 2012 06:39:22 -0700 (PDT)
X-BeenThere: backbonejs@googlegroups.com
Received: by 10.236.73.226 with SMTP id v62ls689912yhd.7.gmail; Wed, 16 May
 2012 06:39:20 -0700 (PDT)
Received: by 10.236.170.66 with SMTP id o42mr226246yhl.11.1337175560630;
        Wed, 16 May 2012 06:39:20 -0700 (PDT)
Date: Wed, 16 May 2012 06:39:19 -0700 (PDT)
From: Vova Pjatochkin <vovapjatoch...@gmail.com>
To: backbonejs@googlegroups.com
Message-ID: <12080105.1523.1337175559825.JavaMail.geo-discussion-forums@ynjm4>
In-Reply-To: <6217128.931.1337165078867.JavaMail.geo-discussion-forums@vbym15>
References: <6217128.931.1337165078867.JavaMail.geo-discussion-forums@vbym15>
Subject: Re: Best practice for data model access
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1521_15205231.1337175559812"

------=_Part_1521_15205231.1337175559812
Content-Type: multipart/alternative; 
	boundary="----=_Part_1522_18513853.1337175559823"

------=_Part_1522_18513853.1337175559823
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

the central place to put all objects - is your application object

=D1=81=D1=80=D0=B5=D0=B4=D0=B0, 16 =D0=BC=D0=B0=D1=8F 2012 =D0=B3., 13:44:3=
8 UTC+3 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=
=D1=8C Ben Gannaway =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
>
> When building a large application, is it better to have a central,=20
> globally accessible set of models and collections, or have every=20
> sub-component initialise models and collections that it needs?
> Instinctively, I felt that a central data set was better, but as my=20
> application has grown, it's starting feel a little unmanageable and I'm=
=20
> wondering what is considered best practice.
>
>
>
------=_Part_1522_18513853.1337175559823
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

the central place to put all objects - is your application object<br><br>=
=D1=81=D1=80=D0=B5=D0=B4=D0=B0, 16 =D0=BC=D0=B0=D1=8F 2012&nbsp;=D0=B3., 13=
:44:38 UTC+3 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=
=D0=BB=D1=8C Ben Gannaway =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:<block=
quote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-le=
ft: 1px #ccc solid;padding-left: 1ex;">When building a large application, i=
s it better to have a central, globally accessible set of models and collec=
tions, or have every sub-component initialise models and collections that i=
t needs?<div>Instinctively, I felt that a central data set was better, but =
as my application has grown, it's starting feel a little unmanageable and I=
'm wondering what is considered best practice.</div><div><br></div><div><br=
></div></blockquote>
------=_Part_1522_18513853.1337175559823--

------=_Part_1521_15205231.1337175559812--