AIA Week 5
Week 5 of Advanced Internet Development at Georgia Institute of Technology

MENU

 

1)

Artificial Project 1 Uninformed and Informed Search Algorithms.

2) Artificial Intelligence Project on Alpha Beta Pruning.

3) Artificial Intelligence

4) Computer Security ( Bell LaPadula Model)

5) Critical Essay and Analysis Part 2

6) Critical Essay and Analysis Part 1.

7) CS8803 AIA @ Georgia Institute of Technology

8) Explicit and Implicit DLL Linking

9) Field Hiding and Method Overriding

10) Fun With Pointers in C++

11) Fun With Pointers in C++

12) India Bollywood News

13) Mathematical Software plotting in maple and matlab coming soon

14) CS 8803 AIA Paper 2Title: Sleepers and Workaholics: Caching Strategies in Mobile Environments.

15) CS 8803 Week 3 Paper Critque

 

CS 8803 AIA
[3.0 AS] 34
Problem Statement:

The purpose of this paper is to present to the readers 
OpenCQ which is a continual query system for
update monitoring in the web. The paper begins with 
the importance of continual query: It's quite
inefficient to continuously re-execute the query, 
particularly when the underlying data hasn't
changed. This is especially true when working with 
obscure stocks that may change only a few
times during the trading day. The domain of continual 
query is defined over past, present and
future data sets where as the domain of pull queries 
are limited to past and present data. The
central theme of the paper is to put forward the 
semantics of continual query used in
OpenCQ, over the two divisions of 1) semi structured 
data and 2) trigger specification.

Strengths:

The main strengths of the paper are that in the first 
half it presents the concept of a continual
query independent from OpenCQ. This allows the user to 
comprehend the importance of
continual query when the GUI of an application requires 
constant refresh of data but re-executing
a pull based query is expensive. Based on this problem, 
continual query is the solution. On this
premise, the paper now presents the design and 
implementation of OpenCQ which utilizes
continual query. In the 2nd half of the paper, the 
author reemphasizes the design goals of
OpenCQ, it is scalable for a large number of continual 
queries on distributed trigger
processing. From a very top level, this is achieved by 
grouping continual queries based on their
trigger structure i.e. explained in great detail in 
section 4.0 of the paper. Other highlight of the
paper is on the modularity of OpenCQ. The system as 
much as possible utilizes software
engineering methodologies in modularizing the components 
of OpenCQ such that futurecomponents can be built by 
reusing conventional DBMS components. This allows high 
cohesion
and to a certain degree low coupling.

Suggestions:

A personal suggestion is that the author should and must 
have evaluated contemporary continual query systems and 
the advantages that OpenCQ has over these other continual 
query systems.
The major theme of the paper is to compare OpenCQ over 
pull based queries, but a more robust performance/comparison 
style would be to compare 
and contrast with other conventional
continual query systems.I compared this paper with 
CONQUER 'A continual query system for Update Monitoring 
in the WWW' by the same author, in which they introduce 
CONQUER. A side by side comparison between CONQUER 
and openCQ may be another potential area of research 
work. This will allow the reader and other researcher to
evaluate CONQUER and openCQin a different light and 
at the same time understand semantic distributed trigger 
structures that CONQUER may surpass other continual 
query systems.