TeleScope CQ Icon

TeleScope CQ

beta

XML Message Stream Continuous Query (CQ) Platform

2 Recommendations
1 Download (This Week)
Last Update:
Download telescope-1.0.1.tar
Browse All Files
Linux

Screenshots

Description

TeleScope CQ is the efficient intensive-load XML message stream broker and simple event processing platform (SEP) written in C for the Fedora 17-18, Slackware 13-14, Red Hat Enterprise Linux 6 (RHEL-6) Linux distributions.
The platform is intended to be operated upon the single number/word values and is not meant to be deployed for full-text XML stream analysis. TeleScope has internal query language with a set of standard logical operators that allows to construct relatively complex query expressions. The platform features the pub-sub architecture and serves up to 128 simultaneously connected XML stream subscribers. The broker features Continuous Query (CQ) engine over the XML message stream. TeleScope CQ provides the remote cli interface to login (in cisco fashion via telnet) and change/reset the query transaction on the current stream on the fly in real time. It also gives data query and subscribers statistics via a separate status port.

TeleScope CQ Web Site

Features

  • Extremely fast real-time XML stream processing
  • Publish-Subscribe architecture
  • Pub-Sub model with support for a large number of concurrent stream subscribers
  • Efficient Continuous Query Engine
  • Dynamic Transaction Processing on the fly
  • Real-time query statistics support
  • High-bandwidth load tolerance
  • Dual mode operation - both subscriber and publisher or either one
  • XML stream filtering and reprocessing in a nodes chain (content distribution mesh via the overlay network creation)
  • Loading of XML data from the data file for publishing
  • Thread Pool subscribers management mechanism
  • Queue based publications management
  • XML processing powered by the Gnome Libxml2 library
  • query language is simple and more intuitive then existing XQuery alternative
  • Fair Queuing of XML messages to all subscribers
  • could be deployed as simple event processing system (SEP)
  • Is different from traditional messaging applications supported by message-oriented middleware for Enterprise Application Integration (EAI)
  • Used in the environment where messages in the XML stream need to be content-processed in real time while they pass through main memory
  • Does not perform message transformation

Update Notifications





User Ratings

 
 
2
0
Write a Review

User Reviews

There are no thumbs down reviews.

Additional Project Details

Icons must be PNG, GIF, or JPEG and less than 1 MiB in size. They will be displayed as 48x48 images.