Confirmed users
385
edits
User:Anaaktgeboren/SearchEngineSync: Difference between revisions
→Current Suggestions/Notes
| Line 37: | Line 37: | ||
** should it be applicationID based, the way addons? | ** should it be applicationID based, the way addons? | ||
** should we limit to a blessed type of plugin to address hijacking? | ** should we limit to a blessed type of plugin to address hijacking? | ||
** what data represents a search plugin? | ** what data represents a search plugin? and where are the keywords assoicated with it? | ||
* Digging notes | * Digging notes | ||
| Line 65: | Line 65: | ||
** why do google/bing end up with duplicate entries in the search table? if a keyword is used a new row is added except value is the keyword? | ** why do google/bing end up with duplicate entries in the search table? if a keyword is used a new row is added except value is the keyword? | ||
** what does used mean in the sql table? in the name column? | ** what does used mean in the sql table? in the name column? | ||
** design pondering | |||
*** Should this be like tabs and a one-record /client | |||
*** or breakdown the table's multiple entry, grab the json and make it one record per 3rd party (but what about ordering of defaults?) | |||
*** treat the table & the json as entirely separate things, essentially two record types? tis not really the sync way and I do not even know if it is feasible | |||
*** do i extract the values of the json blob and rebuild it on the client, or send the thing over the wire wholesale? | |||
== Design & Design Review == | == Design & Design Review == | ||