You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Embedded proxy (starts in code as Java object etc)
Rest proxy (starts as java process and all interactions are using REST requests)
Overview:
Embedded proxy works much more faster and lots of projects were integrated with enbedded one due to the performance issues with REST.
[LIMITATIONS]
There is no chance to automate process of proxy configuration on device (except of script which navigates using appium, it can be implemented in future I think):
all existence sollutions are unstable (even for Android);
Devices are pre-configured (proxy is configured manually);
Devices have no access to the i-net due to stopped proxy;
Possible issues in case of lots devices are configured to one host (not sure here, there is an example with ~15 proxies and it works);
Separate pools of devices for proxy (not)based devices: since with proxy it works a bit slower than without.
[IMPLEMENTATION]
Core functionality to start/stop/configure proxy (partly implemented but I'm not sure it work in latest cores, but anyway it should be re-implemented);
Capabilities matcher to filter devices with/without proxy (it can be done a bit later);
Free port resolver: to stop processes in case port is in use;
...
The text was updated successfully, but these errors were encountered:
[BMP intergration]
[There are two possible ways to implement it]:
Overview:
Embedded proxy works much more faster and lots of projects were integrated with enbedded one due to the performance issues with REST.
[LIMITATIONS]
all existence sollutions are unstable (even for Android);
[IMPLEMENTATION]
The text was updated successfully, but these errors were encountered: