Vragen
+2
Beantwoord
(Full) Site licenses
Theo Derks - NL (distributor) 9 jaar geleden
in Licensing and marketing
•
bijgewerkt door Ekaterina (head of support) 9 jaar geleden •
6
We discovered a big problem with Full Site Licenses and Site licenses.
To check the license, a socket-connection is setup to the specific IP-interface (for example KNX BAOS). After checking the serial from the BAOS, the socket-connection is continuously in use.
This means that if an installer is using a (Full) Site License for KNX & BAOS, the theoretic number of licenses is unlimited, but the technical number of licenses is limited to 10 (in case of using the BAOS).
Our questions:
- Why is -during checking the license- the socket-connection continuously in use, and not -after checking the license- close the socket, so these sockets are free for new requests?
- How to solve this problem with a work-around? In other words: if an installer has a project with > 10 devices (for example with KNX): how to solve this problem with a (Full) Site License??? Because nobody now is able to use a (Full) Site License for KNX with a number of control panels > 10 !!!!
Please let us know how to solve this.
Thanks Theo
To check the license, a socket-connection is setup to the specific IP-interface (for example KNX BAOS). After checking the serial from the BAOS, the socket-connection is continuously in use.
This means that if an installer is using a (Full) Site License for KNX & BAOS, the theoretic number of licenses is unlimited, but the technical number of licenses is limited to 10 (in case of using the BAOS).
Our questions:
- Why is -during checking the license- the socket-connection continuously in use, and not -after checking the license- close the socket, so these sockets are free for new requests?
- How to solve this problem with a work-around? In other words: if an installer has a project with > 10 devices (for example with KNX): how to solve this problem with a (Full) Site License??? Because nobody now is able to use a (Full) Site License for KNX with a number of control panels > 10 !!!!
Please let us know how to solve this.
Thanks Theo
Antwoord
Antwoord
Beantwoord
Hello, Theo,
In the near future we don't plan to change this. We can return to discuss after releasing of Server.
Sincerely yours,
Oksana Storozheva
iRidium mobile Team
In the near future we don't plan to change this. We can return to discuss after releasing of Server.
Sincerely yours,
Oksana Storozheva
iRidium mobile Team
Hello Matthijs
It is not a problem of iRIdium, it's a limit of KNX interfaces, how should we solve an external problem? When iRidium Server will be released, you'll solve this problem using Server, but now it is not possible. We can return to discuss after releasing of Server.
It is not a problem of iRIdium, it's a limit of KNX interfaces, how should we solve an external problem? When iRidium Server will be released, you'll solve this problem using Server, but now it is not possible. We can return to discuss after releasing of Server.
Hi to all,
it can be fixed easy.
When the license is checked on the BAOS-IP interface, a socket is used.
The probem is, that this socket is 'in use' during the whole time iRidium App is active on client.
The solution is simple:
after checking the license, delete the socket to the BAOS and then the socket is free after 2 minutes for the next iRidium client that want to check the license.
In this case the number of connected clients is unlimited, because after checking the license the socket (connection) to the BAOS is broken.
Simple and everybody is happy.
Thanks
Theo
it can be fixed easy.
When the license is checked on the BAOS-IP interface, a socket is used.
The probem is, that this socket is 'in use' during the whole time iRidium App is active on client.
The solution is simple:
after checking the license, delete the socket to the BAOS and then the socket is free after 2 minutes for the next iRidium client that want to check the license.
In this case the number of connected clients is unlimited, because after checking the license the socket (connection) to the BAOS is broken.
Simple and everybody is happy.
Thanks
Theo
Theo, not everybody. This method is not safe for us in case of commercial usage by our opinion, so we don't plan to update the current licensing system. It will be realized with server OR with new "cloud" licensing.
Customer support service by UserEcho
In the near future we don't plan to change this. We can return to discuss after releasing of Server.
Sincerely yours,
Oksana Storozheva
iRidium mobile Team