Jobeet: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Original Function == | == Original Function == | ||
"[http://www.ens.ro/2012/03/21/jobeet-tutorial-with-symfony2/ | "[http://www.ens.ro/2012/03/21/jobeet-tutorial-with-symfony2/ Jobeet2]" is what the Symfony developers call an example app that is a jobs site used as a model use case of their framework. | ||
* [http://www.intelligentbee.com/blog/?s=jobeet Chapters up to 19] for Symphony 2. | |||
* [http://symfony.com/legacy/doc/jobeet/1_2?orm=Propel Original Jobeet (Symfony 1)] | |||
== Meaning Here == | == Meaning Here == | ||
Revision as of 13:56, 9 January 2014
Original Function
"Jobeet2" is what the Symfony developers call an example app that is a jobs site used as a model use case of their framework.
- Chapters up to 19 for Symphony 2.
- Original Jobeet (Symfony 1)
Meaning Here
In the context of my softwares, Jobeet is a warping of the original use case to display an existing biz case and create, expand, or deepen a line of biz by using the original function to find buyers for similar development or workers that have done similar work.
Carries Symfony-Drupal Salient
DS users (initially just my clients) will be able use my space without registration by supplying a single secret, generally known on a group basis. They then can access any resource for which they know another group secret, supplied either operationally and implicitly such as in a URI path member or explicitly bu supplying the role name/id secret.
Primary user identification is performed by a third party or transmitted cert.
