Artur Hefczyc opened 1 decade ago
-
The Web client may need to do resource binding though.
is this a requirement that the script could either bind resource or leave it up to the client (e.g. if no resource is provided or the option is selected)?
Approach with mimicking regular bosh session creation seems good; I think that for adhoc and creating authenticated bosh session I would need around 10-12h.
As for the REST - there is already handler that could handle already present ad-hoc (Andrzej, could you confirm?) thus it won't be explicitly necessary.
-
is this a requirement that the script could either bind resource or leave it up to the client (e.g. if no resource is provided or the option is selected)?
Unless there is a reason for not having the option available I think it is always better to have the option.
| Type |
Task
|
| Priority |
Major
|
| Assignee | |
| RedmineID |
1669
|
| Version |
tigase-server-7.0.0
|
| Estimation |
0
|
| Spent time |
0
|
Not sure if this is already submitted.
We need an admin command (ad-hoc and REST API) to create SM user session and Bosh session for a web client and return Bosh session ID and RID back as a result of the command. So the web client can just connect using Bosh session ID without authenticating. The Web client may need to do resource binding though.
Maybe the simplest way to implement it would be to add an admin ad-hoc command to the Bosh component which would run more or less initial user session creation steps similar to a normal Bosh client login.
Please estimate work effort and based on this we will decide whether it goes to version 5.2.0 or later. Maybe Andrzej can have some suggestions for this?
Take into consideration: http://metajack.im/2009/12/14/fastest-xmpp-sessions-with-http-prebinding/