We currently have two solutions on one server that use each other as external data sources. Despite having one browser window open, if you look at the client in the admin console, it shows 2 open DBs. Would that count as one concurrent connection or two?
Specifically, is a concurrent connection a connection to the server, or a connection to a specific file on the server?
Keep in mind that a concurrent connection only applies to FileMaker Go 13 and FileMaker WebDirect clients when used with FileMaker Server 13.
So in your scenario above you are not burring ANY concurrent connections at all.
Confused. I was referring to a client accessing a solution on server via a web browser
Ah...let me take another crack at this then.
If I access a solution using FIleMaker WebDirect that has twenty (20) related files, that counts as one (1) concurrent connection as I am really only accessing one of those files at a time if you think about a SDI (single document interface) interface which is inherent when using a web browser. So even though I might have twenty (20) files open, in reality I have one (1) open and nineteen (19) open in the background.
Now, if that same user opens another tab in their browser and opens another FileMaker WebDirect file / solution then that would count as a second concurrent connection within the same browser.
When it comes to FileMaker WebDirect, thinking in terms of SDI should make questions like this a little easier to wrap your head around.
This knowledge base article might answer any additional questions that might pop up
Thanks Steve. I was leaning toward that being the correct answer. The confirmation surely is a load off my mind.