Virtualized browser apps such as Puffin Browser and Flashfox allow mobile devices to playback and interact with Flash and other restricted content.
To my understanding, this is achieved through an RDP-like protocol which effectively means a browser is launched on a cloud server and streamed back to the client app.
However, my confusion comes with my limited use of remote desktop software. Typically, opening an RDP/VNC connection will launch a full-experience shell, sharing the entirety of the GUI including the desktop, menus and application chrome. Instead, only the viewport of a browser session should be shared.
Additionally, how is the user sandboxed to the browser viewport? How are they prevented from right-clicking, opening new tabs, invoking application menus, tabbing to other applications or launching the Start menu, etc.?
I'm not expecting a full break-down of the software and configuration required to achieve this; I'm happy to investigate that myself. I would simply appreciate some pointers to guide me in the right direction.
Related
We are working on building a web application using ACS that would be accessed through the desktop as well as mobile devices. We've found a way to render the local and remote video on the screen from the desktop computers, unfortunately, there is no video stream being transmitted when using the website calling through the iPhone. Not sure if this might be the camera device selection problem, in all instances we use
const videoDeviceInfo = cameras[0];
We then proceed to pass in the videoDeviceInfo into the call that is initiated. Any ideas on what might be missing on safari that's working on the desktop would be highly appreciated!
so I got a bit of a weird question. Fiddler captures traffic perfectly with apps like chrome or discord, but when I open a game such as roblox or geometry dash, fiddler does not capture any traffic from these apps. Any way around this or another app that can sniff traffic from apps properly?
Fiddler is a proxy server which, when started, should work without additional configuration with apps that respect the Windows networking configuration.
Some applications are not respecting them though, so if you need to debug their traffic, you should explicitly configure them (if possible at all) to use the Fiddler proxy, which is by default on 127.0.0.1:8888.
Im making an app that multiple players can connect to, but im brainstorming the best approach.
Im going to be using electron for the interface and then be able to use other computers to log in to website to join the game with multiple players.
I will use sockets to connect to each player, but what i am trying to figure out is whats the best approach for the interface.
Should i use express with electron to somehow connect to the same website the players are on?
Is it possible to make the electron app start up a server and have my website direct to the computer that is running the electron app?
Or my other option was to just continuously upload and download from a database, but I feel like that would not be very efficient.
You're on the right track. I would suggest using a WebSocket based server / client architecture.
The server application is continuously running and handles inter-player communication as well as providing a database. The database could be integrated in the server application as a starting point, and, depending on your needs concerning scalability, be extracted as a standalone service in the long run.
Client applications could then come in many forms (a website, a desktop application, a mobile app). Using electron is a great way to enable cross-platform desktop application development that is adaptable to any of these scenarios, possibly also enabling to extract the contained web application as either a hosted website or even mobile application (using, for example, react-native or nativescript).
Good luck!
We assume the answer is no. However, all SO questions are either dated or based on desktop browsers.
We're aware of WebRTC, but it's not supported in Mobile Safari today. Is there any other approach?
To clarify the scenario, imagine we had a service like Skype. Instead of requiring both parties to have the app, we would like one side to use a mobile browser to have phone calls.
No, you cannot. Not without plugins. If you want to place calls from a browser to any other client, you must use WebRTC for full support (media transport + media devices access) or you have to use a plugin to access the media devices and to do the transport (e.g. Flash).
As Mobile Safari still don't have WebRTC...
I'm behind a corporate firewall and all network traffic goes thru the main proxy. In my iOS simulator, I get proxy popups a few times each time I run my app. The thing is, my app doesn't make any network calls (yet), and doesn't import any network frameworks. In fact, I can reproduce this by making a new project in XCode using one of the standard templates and run it straight away; it'll still prompt for the proxy credentials every time.
In my OSX network settings, I've obviously set my proxy credentials in all the different protocols (HTTP, HTTPS, FTP, Socks, RTSP, Gopher). I found that I needed to put the domain and backslash before my username to allow web access in any OSX browsers etc...so given that I did that and then the OSX proxy prompts went away and I was allowed access, I would have thought that the iOS simulator would just inherit those settings...?
Any ideas?
One more bit which may be unrelated: we haven't yet figured out how to get access to the App Store on this Mac; despite supposedly getting past the proxy, any use of the App Store just results in timeouts and we can't even see the "home page". I'm wondering if somehow the iOS simulator is making similar network calls using some other protocol that is like the App Store...? (I would have thought App Store would have been HTTPS but I don't know).
Any thoughts appreciated.
If you put *.apple.com in your proxy passthrough list, the simulator will stop whining about it.
Like you, I can't get the Apple Store to work through our corporate proxy either. I've worked around it by using a wireless network that doesn't use a proxy when I have to use the App Store.
I've found plenty of other things in the OS that don't work through our proxy.
I had the same issue and found another way without touching the proxy settings!
I'm working on a Mac with OSX-El Capitan so maybe in other versions these steps might be slightly different:
Go to System Preferences
Go to Network
Choose your connection (Wireless/Ethernet/Thunderbolt-Ethernet)
Click on Advanced Options
Go to the tab Proxies
The two boxes Automatically detect proxy (for the internet connection on your mac) and Web-Proxy (HTTP)
Insert your login credentials at Web-Proxy (HTTP).
This reduced the occurence of the Proxy-PopUp greatly on all the 3 macs I work with. (At least it doesn't appear periodically anymore when I start my app from xcode)