mirror of
https://github.com/kerberos-io/documentation.git
synced 2026-08-23 15:18:31 +00:00
@@ -14,7 +14,7 @@ IP cameras have outnumbered the video camera industry, they come with many diffe
|
||||
|
||||
### Desire
|
||||
|
||||
What we often see is that users ask for, or desire to have, one single application where they can access and manage all there different IP cameras. This desire may look obvious at first sight, but has **limitations on the long run**.
|
||||
What we often see is that users ask for, or desire to have, one single application where they can access and manage all their different IP cameras. This desire may look obvious at first sight, but has **limitations on the long run**.
|
||||
|
||||
Many video surveillance solutions, other than Kerberos.io, uses the approach previously described. However this approach is against the Kerberos.io strategy/philosophy, read more about it on the [**strategy page**](/strategy) and the [**one vs multi camera support**](/strategy#one-vs-multi) discussion.
|
||||
|
||||
@@ -49,4 +49,4 @@ If you consider to connect multiple local cameras to a processing unit (server,
|
||||
* Did you positioned your cameras properly?
|
||||
* Has the second (or other) camera a lot of value? Maybe can you give it a better position somewhere else.
|
||||
|
||||
In most of the cases a second or third camera can be of a lot of value e.g. a 360° view. However in most of the cases this is totally overkill and you should better use it at a completely other position.
|
||||
In most of the cases a second or third camera can be of a lot of value e.g. a 360° view. However in most of the cases this is totally overkill and you should better use it at a completely other position.
|
||||
|
||||
Reference in New Issue
Block a user