How do I prevent fullscreen to create its own space or how do I create a keyboard shortcut to such a fullscreen space

Question

Hello,
    In Mountain Lion, I could select from the dock icon the Options -> Assign To -> This Desktop to link back a fullscreen app to one desktop which allowed me to have a direct shortcut to my fullscreen app, e.g. ⌘3. In Mavericks this does not work and I cannot find how to disable the new space for fullscreen app nor how to create a keyboard shortcut for switch directly to that app once it's in fullscreen.
    Any help would be much appreciated, I would hate to have to downgrade back to Mountain Lion.
Cheers,
kybus

Answer 1

The most typical solution for enterprise sites is to store their users credentials in an LDAP store such as Oracle Internet Directory (OID) or MS Active Directory. LDAP is an industry standard for extremely fast directory services over IP network infrastructure (http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol).
In turn some sites store their user credentials in databases tables. Of course databases can be configured for fast lookups too, but it is a database centric solution where LDAP is designed to work across networks and is ideal for servers as a result which live and breath on the network.
In case of Java EE applications and especially those written in ADF, the use of these services isn't written into the application, but rather the application delegates this responsibility of configuring and providing these services back to the Java EE server. So for example Edwin's post is about configuring a WLS "security provider" to lookup user's info from the database, and here is another blog I wrote for MS Active Directory a while back (http://one-size-doesnt-fit-all.blogspot.com.au/2008/12/configuring-wls-with-ms-active.html). The main advantage here is you don't have every application baking its own solution, rather WLS provides a standard well tested way to configure the security lookups.
In terms of writing (i.e. creating users) to the security store over reading from it, indeed you need to build your own code. Ramandeep Singh Nanda has a nice post on doing this with OID through Oracle's OPSS: http://ramannanda.blogspot.com.au/2011/09/opss-adf-security-utility.html
Finally what sites like Amazon and Facebook do aren't necessarily good examples to follow as they're application's requirements are typically far in excess of a typical enterprise site, and in turn have often written bespoke solutions to deal with their scalability and distribution requirements. I dare say LDAP is a good choice for 99% of enterprises.
CM.