General question - If I have very large entities with information that
varies in usage, should I split the information I use less into another
entity?
I'm creating fairly large entities (column wise) and was wondering what
the proper strategy was to approach storing the properties. An example
is,
Hey fellas,
I've created multiple applications for basic functions, blog/forums/
chat that I want to share across 3 or 4 domain specific applications.
Is there a way that I can have a user sign into one application and
also automatically sign them into the other applications? So that way
if they'r
Was trying to look around for an answer and couldn't find it, but if I
owned several applications, could i create a single sign on page that
would log into both applications at the same time? For example, if i
had a blog type of web site and I wanted to integrate it with a forum
application I had,
