Asher 1164801376 Keep a maximum number of connections instead of a timeout ... There's no way to actually know if those clients have gone away, so it seems it might be better to base it on whether the user has connected again with new clients to determine if the old clients are now invalid.		2019-09-09 16:41:04 -05:00
..
login	Target a recent commit for VS Code	2019-08-29 19:11:11 -05:00
media	Target a recent commit for VS Code	2019-08-29 19:11:11 -05:00
api.ts	Add package.json for publishing API types	2019-09-04 11:47:50 -05:00
channel.ts	Target a recent commit for VS Code	2019-08-29 19:11:11 -05:00
cli.ts	Add version format flag	2019-09-04 17:01:06 -05:00
client.ts	Target a recent commit for VS Code	2019-08-29 19:11:11 -05:00
connection.ts	Keep a maximum number of connections instead of a timeout	2019-09-09 16:41:04 -05:00
insights.ts	Add environment variable for telemetry endpoint	2019-09-05 15:26:35 -05:00
ipc.ts	Update VS Code to 1.37.0	2019-08-09 19:23:41 -05:00
marketplace.ts	Add tar-stream dependency	2019-08-09 19:23:44 -05:00
nls.ts	Update VS Code to 1.37.0	2019-08-09 19:23:41 -05:00
protocol.ts	Update VS Code to 1.37.0	2019-08-09 19:23:41 -05:00
server.ts	Keep a maximum number of connections instead of a timeout	2019-09-09 16:41:04 -05:00
telemetry.ts	Update VS Code to 1.37.0	2019-08-09 19:23:41 -05:00
update.ts	Detect target automatically	2019-08-21 12:45:09 -05:00
upload.ts	Update VS Code	2019-09-03 17:24:14 -05:00
uriTransformer.js	Make sub-paths work	2019-07-22 18:01:03 -05:00
util.ts	Add version format flag	2019-09-04 17:01:06 -05:00