NO and Studio Customer Complaints - Web based apps and network Issues

serban21 at serban21 at
Tue Mar 7 13:49:34 UTC 2023


Testing on your own is better than nothing, but it might not be enough.
There can be network error on your server Internet connection, but just as
well you can have errors on the client side ISP, on which you have
no control. Not just bandwidth problems, but there can be DNS or latency
issues as well.

There are services such as that can test your
site for various locations and ISPs across the globe (multiple ISPs from
the same location). But it's not for free, and it might be overkill for
you. I'm using that now, but I'm in a corporate environment, and no longer
using Omnis.


În lun., 6 mar. 2023 la 07:00, Stephen Miller <stephenmiller1958 at>
a scris:

> Hi All
> I have been thinking with respect to web-based apps. Developers are really
> losing control over the performance of their apps due to the vagaries of
> the bandwidth at any point in time.
> I, for example, have 5G wireless, and am guaranteed 100 mbps and normally
> get 180 mbps. But today I am getting 20 mbps.
> Got me thinking that developers must be using some independent method of
> testing the bandwidth at any point in time which led me to speedtest dot
> net.
> Ookla has an api for developers which runs on linux and MAC which led to
> this posting.
> I was curious how others do it. Do you just ping your server and a known
> reliable web-site - I use dot com to get a performance base
> normally,  or do you just not worry about it and just take the calls from
> irate customers?
> Kind Regards,
> Stephen Miller
> _____________________________________________________________
> Manage your list subscriptions at
> Start a new message -> mailto:omnisdev-en at

More information about the omnisdev-en mailing list