HaleyAuthority does not impose a physical limit to the number of concurrent users (i.e., rule authors) accessing a single knowledge base. Any issues in such scenarios would most likely stem from the availability of the database managing the knowledge base. However, it is unlikely that the number of rule authors at any given point would be unmanageable, since the rule authoring teams (for a single knowledge base) tend to be small in scale (less than 100).

It is a mistake to measure load on the server in terms of concurrent users. Unlike other protocols, HTTP, the protocol that carries Web traffic does not keep a live connection between a web-based application and its users. Users are not "logged in", but rather initiate a connection when they click on a hyper-link. The connection is broken once the request is served. The whole process typically takes a fraction of a second. A more appropriate measure of a server's load is requests per hour.

Yes. Each transaction is processed separately and there is no limit to the number of "logged in" users.

HaleyRules, our rules inference engine, runs as a component within your application. Versions of HaleyRules are provided for both the .NET and J2EE environments. In addition, the .NET version of HaleyRules (implemented in C for optimum performance) can be used transparently from within a Java application. Many customers choose this implementation to harness the performance advantages of C at rule execution time. HaleyRules Web Services is currently available for Java implementations.

The following concurrent user limitations for the MSDE database and the SQL database are as reported by Microsoft. Small Area Network (MSDE): Microsoft reports the MSDE database supports up to 5 concurrent users performing save functions at one nanosecond at a time. If more than 5 users are performing that same function at that exact nanosecond, the other users function will queue and be processed in the next moment.

Capacity planning depends on many variables. The most important are the inbound and outbound event throughputs, message sizes, maximum latencies. For these reasons we usually suggest to run specific simulations for every provided scenario (as a starting point, we can provide a basic Load Test Toolkit to help run the simulations).

Cardio Server is scalable from 1 to 250 concurrent users. A concurrent user is not a seat license as with some systems. Concurrent users apply to anyone accessing the application simultaneously.

The AP will allow up to some set number of associations before failing to associate new clients. The number is in the the vxworks (or m0n0wall) code, but it, like the hostap and madwifi drivers are, essentially "unlimited". Most code these days introduces a "soft limit" of 1024 associated clients. There is a "hard limit" in that the "Association ID" (AID) space is only "so big".

No application servers are required to run HaleyAuthority or HaleyRules. Should you choose to deploy HaleyRules as a web service, a compatible web server such as Apache Tomcat would be needed. Yes, it is the engine that needs to be available at runtime. Because the HaleyRules engine exists as a Java or .NET object within the application, the engine follows the same HA rules as would any other object made available by the server architecture.

The maximum number of concurrent users that can view reports depends on the complexity of the reports (e.g. number and complexity of the formulas, number of summary fields, number of records fetched from the database, ...) and on the server performance. i-net Crystal-Clear can render approx. 1000 database objects per second on an 800 MHZ machine running WinNT. Yes, if you use i-net Crystal-Clear as a servlet and your web server supports SSL.

Each instance of Solaris PC NetLink 2.0 software officially supports 2,000 concurrent connections from any type of client (such as Windows 95, 98, NT, 2000 and XP) authenticated and attached to the server for file and print operations. This is not a limit in the total number of users, since Solaris PC NetLink software can hold thousands of users in the SAM database. The limitation is on the total number of simultaneous NetBIOS connections to the Solaris PC NetLink server. When a Windows NT 4.

A webserver can only handle a fixed number of incoming requests. A pre-forking server has a limited number of child processes (MaxClients) and a threaded server has a fixed number of threads (MaxThreads). A server can handle up to its maximum number of handlers, no more. Once its handlers are exhausted, socket connections are queued by the OS. They wait for the next available handler.

The more streams you serve, the more bandwidth and memory you will use. Always check the health on the MediaBox with the "Stats" selection. This example was calculated using MP3 streams. When using Real streams you need to purchase an license in order to be able to use more simultaneous streams.

FreeSWITCH has done 3000 concurrent channels with media on a dual woodcrest 2.0 GHz (1 year old). The test was to play back a wav file so there was slight transcoding going on. With current modern cpus you should be able to do 6000 channels per chassis, both because there are 2x the cores as well as 50% additional cycles per core. A dual clovertown (quad instead of dual core) at 3.0GHz should be able to at least double your channel capacity

I have multiple protected directories and each are subdirectories of each other, ie /paid/, /paid/b/, /paid/c/, /paid/c/d/, etc. They are all separately protected by the same group. When a browser goes straight first to /paid/c/ he is prompted once. Then when going to /paid/b/ he is prompted again for the same username/password! I want him prompted only once! I am using files that are played with Windows Media Player.

WebCCTV NVR performance depends on the bandwidth available on the uplink side of the DSL/cable connection. The higher the bandwidth available, the more users can concurrently access the system.

FileZerver can maintain a list of 1,000 known users with approximately 250 concurrent user connections.

Haley supports the JSR-94 specification for the Java Rule Engine API through its rules engine, HaleyRules-JP 5.3. Haley Systems is the first business rules vendor to advance the practical use of JSR-94 by providing a corresponding standard rules syntax.

We license on software based upon the number of concurrent users. For example, if you have 100 employees, you may only need 65 or 75 licenses—since all users will not be using the software at the same time.

No, the USB port will support only one user. If you need to support multiple computers you need to use the Ethernet port and a hub/switch.

Your employees may never need phone-in support because they use a very convenient website for managing their own service. However, your designated system administrator will always be able to call and speak with someone at Reynwood when they need to.

As many as you got. We maintain a series of high-end servers utilizing the latest, most advanced hardware. We also use the largest, most reliable data pipes available to assure our subscribers fast, uninterrupted spam filtering and blocking service.

This depends on the call destination to some extent. Our platform confidently supports about 40-50 calls (under the worst conditions) and about 200-300 calls (under the best conditions). But we've got the capacity to increase our technical facility if needed. top

We don't have a written warrantee, but we will replace anything defective within a reasonable period. After all, the amount of time that people take to complete their kits varies immensely. We have replaced pieces 5 years old. Can I get names of people who have built your kits? Of course. We can frequently find someone right in your area so that you can look at the "real thing" locally. Most owners are willing to talk at length about their experience.

The MPR Series RFID Cards currently support EPC Class 0/0+, EPC Class 1 and EPC Gen 2. ISO 18000-6B and others can be added at a later date. User downloadable utility programs allow upgrades for new capabilities and features.

The Report Server processes report requests one at a time on a first come first serve basis. Example: Five users submit report requests during a one second interval of time, each report takes one second to be generated user #2 waits for two seconds and gets his/her report back (had to wait for user #1's report to be processed and then for his/her own report to be processed) You do have an option to check the number of report requests waiting in the report queue before generating the report.

Wait a half hour or so, and then retry. If the problem persists, ask systems staff for help. The number of S-Plus licenses that we purchase has normally been sufficient.

No, none of the user's names are specified. As long as the Quest Software License Server is correctly installed, the license file and license server mechanism will only count the number of users at any one (consecutive) time, and allocate licenses based on availability.