Analyzed
about 11 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 over 7 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...
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
data presented on the Open Hub is available through our API
-
...
55% of companies leverage OSS for production infrastructure
-
...
you can embed statistics from Open Hub on your site
30 Day SummaryAug 29 2026 — Sep 28 2026
|
12 Month SummarySep 28 2025 — Sep 28 2026
|
