Iโm interested in hearing people who prefer methods or approaches to embed search results from the Google Search Appliance on an existing website. More specifically, how people prefer to embed / embed search results into their existing site and save website elements (menus, memberships, etc.) around the search results.
As far as I know, there are 3 different approaches.
Subdomain, handle everything in xslt - create search.mysite.com, which is completely processed by google xslt and embeds the components of the spatial site in xslt.
Paste search results into an existing site using iframe - Use an existing website and just use an iframe to import the results into the page.
Embed results in an existing site using server-side processing. This is how I previously integrated the search into the site using a combination of custom dev and the GSALib Project .
I would be interested to hear if anyone has any other suggestions and if people were helpful or regretted using the above approaches.
, , . GSA . , , . , , , , , . : . , XSLT? XSLT.
- XSLT XML HTML XML, . , , , .
, , - AJAX , XML JSON .
Source: https://habr.com/ru/post/1750578/More articles:Using the delete element with credentials - powershellUse SmallDateType in Framework-First Entity Framework - sql-serverget text on display with ncurses - cThe right way to text report the remaining time in a long process? - language-agnosticJQuery, hierarchical pagination of a table - jqueryBasic String Encoding X - algorithmUsing vim, how do you quickly refresh the web page you're working on? - linuxNHibernate Named Query Parameter Numbering @ p1 @ p2 etc. - nhibernateWhy is Postgres doing a hash in this request? - optimizationWhat does "(test1, test2, test3 =" 3 ", test4 =" 4 ", test5 =" 5 ", test6 =" 6 ")" do? - ruby โโ| fooobar.comAll Articles