Jobeet: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
== Meaning Here == | == Meaning Here == | ||
In the context of my softwares, Jobeet | In the context of my softwares, the Jobeet original use case has been reworked to a completely different use case and a serious production function in my space: | ||
# Job Categories replaced by Lines of Business | |||
# Jobs are actual completed jobs in such lines of business | |||
# CategoryAffiliate is replaced in the model by LoBAffiliate | |||
The first refactoring was complete in early 20114-04. | |||
== Carries Symfony-Drupal Salient == | == Carries Symfony-Drupal Salient == | ||
Revision as of 10:19, 29 April 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, the Jobeet original use case has been reworked to a completely different use case and a serious production function in my space:
- Job Categories replaced by Lines of Business
- Jobs are actual completed jobs in such lines of business
- CategoryAffiliate is replaced in the model by LoBAffiliate
The first refactoring was complete in early 20114-04.
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.
