Top Previous Next |
PageGate can be broken down in to two general sections; input and output. On the input side of things, we have the APIs, which is how PageGate accepts messaging requests from a variety of sources. On the output side of things, we have the Carriers and Connectors. The carriers tell PageGate what communication method to use and the connectors are directly responsible for negotiating those communication sessions.
This section configures the basic behavior of the connectors as well as displays the general status of all connectors.
These sections control certain communication settings of the connector referenced.
In concept, a connector in PageGate is just a pathway to deliver messages as any connector in the program can, in most cases, handle any protocol at any time. So, you could implement a series of SMTP, WCTP and WCTP carriers and have all traffic processed through a single connector. However, each connector can only establish one message delivery sequence at a time. Also, each protocol has its own average negotiation time.
So, as an example of how to work out the math on how many connectors you may need, let's say that you wanted to deliver 400 SMTP based messages.
At a delivery rate of 1 message every 4 seconds, it would take approximately 1600 seconds (or 26.66 minutes) for a single connector to deliver all 400 messages. If you had two connectors, that would take approximately 800 seconds (13.33 minutes), if you had three, it would take approximately 533 seconds (8.88 minutes) and so on.
|