This depends in part on your operating system. There is however no limit on a specific port. There is a limit on the number of concurrent connections however, typically limited by the number of file descriptors the kernel supports (eg 2048). The thing to remember is that a TCP connection is unique and a connection … Read more
It seems to me that you should construct the unique ID corresponding to your requirements. This ID can be constructed as a hash (like MD5, SHA1 or SHA512) from the information which is important for you (some information about software and hardware component). You can make your solution more secure if you sign such hash … Read more
Couple of considerations for choosing one big vs several small: In the single request case, you can’t do progressive data processing as the data arrives; you need to wait for the full packet to arrive before you can do anything. If it fails, you need to start everything from scratch. In the multiple requests case, … Read more
Sorry that this isn’t directly answering your question, but generally speaking you shouldn’t rely too heavily on measuring latency because it can be quite variable. Not only that, you don’t know if the ping time you measure is even symmetrical, which is important. There’s no point applying 10ms of latency correction if it turns out … Read more
Instead of speculating I decided to make some benchmarks that you can run on your own server, to see what’s the answer to that question in your case. I will also include the results of those tests that I got on my computer which are quite interesting. Preparing for tests First, what I did and … Read more
The code is right. The only mistake was that I was trying to start the service twice once in onServiceConnected() method and the other in onCreate() method. I changed my code to start the service only in onCreate() method in the launcher activity. The rest of the activities directly bind to the service by using … Read more
Server-side cache control headers should look like: Expires: Tue, 03 Jul 2001 06:00:00 GMT Last-Modified: {now} GMT Cache-Control: max-age=0, no-cache, must-revalidate, proxy-revalidate Avoid rewriting URLs on the client because it pollutes caches, and causes other weird semantic issues. Furthermore: Use one Cache-Control header (see rfc 2616) because behaviour with multiple entries is undefined. Also the … Read more
For a given website / web-application, you can use react either client-side, server-side or both. Client-Side Over here, you are completely running ReactJS on the browser. This is the simplest setup and includes most examples (including the ones on http://reactjs.org). The initial HTML rendered by the server is a placeholder and the entire UI is … Read more
You probably are sending incompatible datatypes: per the client-server communication documentation, requests with Dates will fail. My preferred method for google.script.run communication is to 1) send all Dates as milliseconds, via Date().getTime(), as this will also avoid timezone issues and browser-dependent datestring parsing differences. In the client then, you can remap your input data back … Read more
You want to use the wm_protocol method of the toplevel window. Specifically, you are interested in the WM_DELETE_WINDOW protocol. If you use that method, it allows you to register a callback which is called when the window is being destroyed. Usage: root.protocol(“WM_DELETE_WINDOW”, app.on_delete)