wojciech.kapcia@tigase.net opened 10 years ago
|
|
I implemented support for:
In each of this setting as entry which should be trusted it may be passed jid which may include
and we would have 2 cluster nodes
If another cluster node will connect then property will be updated for this newly added node.
However this change required me to implement Now looking at currect implementation of methods |
|
I've updated PubSub ad-hocs to use changed code and now it works as expected. Another issue I've encountered - if there's no script then there is no response to the sending entity - I think returning item-not-found in that case -- %kobit , do you agree?
I think this is a good idea - would definitely simplify the implementation. |
|
Actually - TTS test fails (repo reloading): http://build.tigase.org/nightlies/tests/files/static/tests/7.1.0-SNAPSHOT-b3973/func/pgsql/functional-tests.html after latest changes. |
|
I fixed issue found during TTS test |
Type |
New Feature
|
Priority |
Normal
|
Assignee | |
RedmineID |
3244
|
Version |
tigase-server-7.1.0
|
Estimation |
8h
|
Spent time |
9h
|
Add option that will append list of all/chosen components addresses within cluster to the
trusted
list, as to avoid manual modification of configuration file, as per:https://projects.tigase.org/projects/tigase-pubsub/wiki/REST_API