![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to Database Applications T network, including at OC48 routers, for detailed monitoring. In this paper we describe our motivation for and constraints in developing Gigascope, the Gigascope architecture and query language, and performance issues. We conclude with a discussion of stream database research problems we have found in our application. @inproceedings {DBLP:conf/sigmod/CranorJSS03, author = {Charles D. Cranor and Theodore Johnson and Oliver Spatscheck and Vladislav Shkapenyuk}, booktitle = {SIGMOD Conference}, title = {Gigascope: A Stream Database for Network Applications.}, pages = {647-651}, year = {2003}, url = {db/conf/sigmod/sigmod2003.html#CranorJSS03}, ee = {http://www.acm.org/sigmod/sigmod03/eproceedings/papers/ind03.pdf}, crossref = {conf/sigmod/2003}, bibsource = {DBLP, http://dblp.uni-trier.de} } ![]() ©2004 Association for Computing Machinery |