The search engine that I use to index the content has a connector for Lotus Notes that sucks the content out using the Notes API. This works very well for Domino servers that are hosted on our internal network.

The Twisty problem still causes an issue when a document from a user search is viewed. At this time, the doc is generated as HTML by Domino and streamed through the search engine so that keyword highlights can be added etc. The users get annoyed when the search engine returns results that they can't immediately see because they are hidden in a twisty.

Another problem is that there are a large number of Domino servers hosted elsewhere (external hosting provider etc.) that I cannot connect to using the Notes API. These servers must be indexed via HTTP and the representation of the 'ExpandSection' argument plays havoc with the indexing. The search spider views each version of the URL as a new document.

The 'ExpandAll' argument is something that Domino web developers have been asking about for years. Lotus just couldn't do it in R5 and it can't be done using LotusScript. The Perl app that I am developing is the most recent in a long line of potential solutions.

In reply to Re: Re: Domino Twisty Expansion using Lightweight Proxy by inman
in thread Domino Twisty Expansion using Lightweight Proxy by inman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.