Clash for Windows 是基于 Clash Core 开发的 Windows 平台代理工具，支持 Shadowsocks(R) / V2Ray / Trojan / Socks5 / HTTP(S) 等代理协议，支持策略组及规则分流。
下载地址： Github Releases
第一次使用？查看 快速上手
在配置好 Clash for Windows（下文略称为 CFW ）后，我们可以考虑开启 Allow LAN （局域网代理共享），以便处于同一局域网内的其他设备接入到本机代理环境中。这不仅可以节省在多台设备中重复部署代理软件的时间，同时也可以通过 CFW 内置的 Connections 对局域网内设备的网络情况实时地管理与监控。
| Param( | |
| $solrVersion = "6.6.2", | |
| $installFolder = "c:\solr", | |
| $solrPort = "8983", | |
| $solrHost = "solr", | |
| $solrSSL = $true, | |
| $nssmVersion = "2.24", | |
| $JREVersion = "1.8.0_151" | |
| ) |
Next.js, Nginx with Reverse proxy, SSL certificate
| // ==UserScript== | |
| // @name Stack Exchange hotness estimator | |
| // @namespace http://vyznev.net/ | |
| // @description Estimates how highly each Stack Exchange question would rank on the Hot Network Questions list | |
| // @author Ilmari Karonen | |
| // @version 0.4.5 | |
| // @license Public domain | |
| // @homepageURL https://meta.stackexchange.com/a/284933 | |
| // @downloadURL https://gist.github.com/vyznev/bb2c1adb6e96eb65a87bab3822c74e81/raw/se_hotness_estimator.user.js | |
| // @match *://*.stackexchange.com/questions/* |
| #!/bin/bash | |
| # Why? Education & zero redis-cli dependecy | |
| # (it is a shame, however, that this functionality isn't a part of redis-cli... PR on the way) | |
| HOST=127.0.0.1 | |
| PORT=6379 | |
| if [ $# -lt "2" ] | |
| then | |
| echo "Call a Redis command with its last argument being file contents" | |
| echo "Usage: $0 <Redis command> <keys and arguments for command> <payload>" |
The content from this GIST has been moved to official Azure Cache for Redis Documentation. The new location is https://docs.microsoft.com/azure/azure-cache-for-redis/cache-troubleshoot-client
Please update your bookmarks.
The CLR ThreadPool has two types of threads - "Worker" and "I/O Completion Port" (aka IOCP) threads.
Task.Run(…) or ThreadPool.QueueUserWorkItem(…) methods. These threads are also used by various components in the CLR when work needs to happen on a background thread.The thread pool provides new worker threads or I/O completion threads on demand (without any throttling) until it reaches the "Minimum" setting for each type of thread. By default, the minimum number of threads is set to the number of processors on a system.
Once the number of existing (busy) threads hits the "minimum" number of threads, the ThreadPool will throttle the rate at which is injects new threads to one thread per 500 milliseconds. This means that if your system gets a burst of work needing an IOCP thread, it will proces
[Google recently announced][poodle] that there is an exploit in SSLv3, this vulnerability is know as POODLE. There is no other option than to disable SSLv3 in order to combat this major flaw. There have already been [guides on how to disable this in different servers][guides]. But nothing excised for Node.js yet, until now. In order to resolve this for Node.js we need to use various of undocumented options and modules.
In the index.js file below you can see an example of how you can protect your HTTPS server
against the POODLE attack. It uses the secureOptions option to pass in constants in to the
SSL context which is created by node.
| import java.io.*; | |
| import java.util.*; | |
| /** The class encapsulates an implementation of the Apriori algorithm | |
| * to compute frequent itemsets. | |
| * | |
| * Datasets contains integers (>=0) separated by spaces, one transaction by line, e.g. | |
| * 1 2 3 | |
| * 0 9 | |
| * 1 9 |
| i | |
| me | |
| my | |
| myself | |
| we | |
| our | |
| ours | |
| ourselves | |
| you | |
| your |
