| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
Add new reset action to admin participant.
Also introduced action buttons (delete and reset).
|
| |
|
|
| |
Logging event creations.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Every participant could GET and POST to this resource.
A GET might show this:
curl ... -H 'Content-Type: application/json' \
-X GET https://ecs.host.com/sys/configs
{
"participant_events": "true",
"resource_events": {
"/campusconnect/glossaries": true,
"/campusconnect/course_urls": true,
"/campusconnect/course_members": true,
"/campusconnect/wikis": true,
"/campusconnect/directory_trees": true,
"/campusconnect/learningmodules": true,
"/campusconnect/groups": true,
"/campusconnect/categories": true,
"/campusconnect/courselinks": true,
"/campusconnect/organisation_units": true,
"/campusconnect/files": true,
"/campusconnect/terms": true,
"/campusconnect/courses": true,
"/sys/auths": false
},
"selfrouting": "false"
}
Only if participant_events and the appropriate resource_events are true,
you will get an event.
It's also possible to set the two attributes participant_events and
selfrouting. Just make a POST such as:
curl ... -H 'Content-Type: application/json' -X -X POST \
-d '{"participant_events":true}' https://ecs.host.com/sys/configs
or
curl ... -H 'Content-Type: application/json' -X -X POST \
-d '{"selfrouting":false}' https://ecs.host.com/sys/configs
or
curl ... -H 'Content-Type: application/json' -X -X POST \
-d '{"selfrouting":false, "participant_events":true}' \
https://ecs.host.com/sys/configs
As you see, just set the attribute you want to set and make a POST.
You don't have to provide a receiver header, because the receiver is
implicitely the ECS.
|
| |
|
|
|
|
|
| |
Up to now events could be turned on and off by resources. To turn on
events you still have to do it by resource but have additionally
the possibility to control it by participant. Only if both switches are
on, the participant will get events generated through the resource.
|
| | |
|
| | |
|
| |
|
|
| |
This was needed because of "extremely critical security fixes".
|
| |
|
|
| |
Initialize code don't have access to model objects.
|
| | |
|
| |
|
|
| |
It's a YAML configuration file for global ECS functionality.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Please use the subresource "details", e.g.
From the viewpoint of a sender you may use:
instead of
curl .... -X GET https://server/<namespace>/<name>/<id>/receivers
use
curl .... -H 'X-EcsQueryStrings: sender=true' -X GET https://server/<namespace>/<name>/<id>/details
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now it's possible to ask for detailed (meta) information of a list resource.
All querystrings supported my normal list resources could be used.
Only the original sender can do that:
curl .... -X GET https://server/<namespace>/<name>/details
You will get back a list of member subresource "details" representations:
[
{
"receivers": [
{
"itsyou": true,
"mid": 1,
"cid": 2
},
{
"itsyou": false,
"mid": 2,
"cid": 2
}
],
"senders": [
{
"mid": 1
},
{
"mid": 1
}
],
"url": "courselinks/10",
"content_type": "application/json"
},
...
]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now it's possible to ask for detailed (meta) information of a posted
message. Only the original sender can do that:
curl .... -X GET https://server/<namespace>/<name>/<id>/details
You will get back something like this:
{
"receivers": [
{
"itsyou": true,
"mid": 1,
"cid": 2
},
{
"itsyou": false,
"mid": 2,
"cid": 2
}
],
"senders": [
1,
1
],
"content_type": "application/json"
}
The "receivers" and "senders" have corresponding arrays: The first array
entry in "senders" has been addressed the first array entry of
"receivers" and so on.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now it's possible to ask for the addressed receivers of a posted
message:
curl .... -X GET https://server/<namespace>/<name>/<id>/receivers
You will get back an array of receiver memberships, e.g.
[
{
"pid": 3,
"itsyou": false,
"cid": 2,
"mid": 2
}
]
pid: participant id
cid: community id
mid: membership id
itsyou: true if the item belongs to you
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The system resources /events, /memberships and /auths are now called
through the sys namesapce:
/sys/events
/sys/memberships
/sys/auths
The old syntax is now tagged as deprecated. All participants are
solicited to change their calling.
|
| | |
|
| |
|
