Open GoogleCodeExporter opened 8 years ago
Original comment by f...@ub0r.de
on 3 Dec 2011 at 8:21
This is strange.
Assuming you do not change any settings, the connector should use the following
requests:
* 1 to check if you are logged in
* if not logged in, a further 2 requests - 1 to do the login and 1 to then
update the balance once logged in
* 1 to update the balance if logged in and you press the refresh button on the
send sms page to update your connector balances
* When checking login if you have changed the "attempt send for free" setting
on the fishtext preferences menu, then 2 requests will be made = 1 to load the
current settings from fishtext, and another to update them.
* To do a send message, the login will be once again checked, then 2 requests
are made to send 1 to load the send message page, 1 to submit the send sms
request. Finally, after a successful send the balance is updated by one further
request.
Sending to multiple recipients or sending long sms messages do not result in
additional requests.
So, for a normal scenario of opening the app when not logged in (or login
expired), then sending a text, there should be just 3 requests made to ensure
you're logged in, and then an additional 4 requests made for each message sent.
If you change the "attempt send for free" option, that would result in 2
further requests as a once-off, next time you send.
Unless there is a bug that is causing some weird http behaviour, I don't see
how the above could be causing fishtext to suspend your account. Further, since
we are just doing http conversations, I'm not sure what they mean by
"disconnects and re-connections".
Could you please ask fishtext for more details on what exactly they are
considering to be "rapid connections" and what they mean by "disconnects and
re-connects"?
There's a lot of people using this connector, so I'm surprised no one else has
had this problem, unless fishtext have changed something recently on their
backend.
Original comment by fint...@gmail.com
on 3 Dec 2011 at 11:22
Original issue reported on code.google.com by
igor.g...@gmail.com
on 3 Dec 2011 at 2:15