Deep Web Technologies redefines the federated search market with its powerful, flexible search solution, Explorit Research Accelerator. Organizations that use Explorit enjoy a custom solution that fits the specific needs of their end users, so searches are not only efficient, they're complete. By combining advanced, real-time search with sophisticated results retrieval, Explorit gives users precise, accurate results delivered with unrivaled agility.
Introduction
On several occasions developing database-driven web applications, I've been approached by clients who want Google-style search implemented at the last minute of the development cycle. Usually this leads to using some canned script that crawls the website, or a hacked up search function that uses the database but either returns too many results or none at all. On top of that, the queries performed are too many or too slow.
Until now, most developers have been forced to use relational databases to power search, install extra component packages, or seek out other non-php solutions. The problem with using a relational database, such as MySql's fulltext indexing, is that scalability problems crop up as your search criteria becomes more complicated.
One of the features that sets the Zend Framework apart from the others is the inclusion of a decent search module. Zend_Search_Lucene is a php port of the Apache Lucene project, a full-text search engine framework. Zend_Search_Lucene promises a simple way to add search functionality to an application without requiring additional php extensions or even a database.
Zend_Search_Lucene overcomes the usual limitations of relational databases with features such as fast indexing, ranked result sets, a powerful but simple query syntax, and the ability to index multiple fields. Better still, a Zend_Search_Lucene index can live happily alongside your relational database to provide fast searching but without duplicating the effort of storing all of your data twice. In this tutorial, I'll show you how to use Zend_Search_Lucene to index and search some RSS feeds.
Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!
B. Yaltaghian, и M. Chignell. CASCON '04: Proceedings of the 2004 conference of the Centre for Advanced Studies on Collaborative research, стр. 308--317. IBM Press, (2004)
Y. Tan, M. Kan, и D. Lee. JCDL '06: Proceedings of the 6th ACM/IEEE-CS joint conference on Digital libraries, стр. 314--315. New York, NY, USA, ACM, (2006)
D. Bollegala, Y. Matsuo, и M. Ishizuka. WWW '07: Proceedings of the 16th international conference on World Wide Web, стр. 757--766. New York, NY, USA, ACM, (2007)
C. Krishnan, S. Rajakumari, и M. Mehraj. International Journal on Recent and Innovation Trends in Computing and Communication, 3 (4):
1750--1754(апреля 2015)