Analyzed
about 22 hours
ago.
based on code collected
1 day
ago.
Project Summary
The aim of this project is to develop a COMET implementation which does not require a custom server, but can run in native IIS.
Most COMET implementations require a custom server as ASP.NET's threading model (pooled threads) does not promote scalability for COMET applications.
Long polling is supported under the Bayeux protocol, using Asynchronous Http Handlers in ASP.NET.
The project uses Jetbrains TeamCity for continuous integration, hosted by CodeBetter.Com
In a Nutshell, aspcomet...
- ...
- ...
- ...
-
...
took an estimated 5 years of effort (COCOMO model)
starting with its first commit in February, 2009
ending with its most recent commit almost 5 years ago
Quick Reference
https://github.com/nmosafi/aspComet
MIT License
Permitted
Commercial Use
Modify
Distribute
Sub-License
Private Use
Forbidden
Hold Liable
Required
Include Copyright
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
learn about Open Hub updates and features on the Open Hub blog
30 Day SummaryMar 19 2024 — Apr 18 2024
|
12 Month SummaryApr 18 2023 — Apr 18 2024
|
