Some thoughts about Index Server
This site is entirely built with controls, and the content from a database.
I'm quite stuck on something, and more I scratch my poor head, less I find a solution.
I have the choice for the search function between using a Full Text in my SQL stuff, or using Index Server, like the oldest version of the project.
Sadly I don't have really the choice with .Net, because of the way that controls are 'virtually' built on request and not physically present like HTML files.
It's quite a surprise for me to see that apparently nobody notice this side effect of controls. If I have an .aspx page, I can indeed wrap an ADO layer to use specific Index Server functions. But what's about content embedded in controls.
The Content Management System I developped use the database obviously but create static controls and page to build the portal.
I do that to avoid overload the data server with many requests. But of course I can't transform my pages in html, I want to keep the flexibility and programming aspect of .Net.
So for the moment, unless someone bring me some ideas, I work with Full Text and I search directly in the database, with the implication that every piece of content has to be store.
And finally what is the future of Index Server, knowing this kind of limitations ?