If both the rails applications are different, then why not to create API call at B's end to return results of a search query. Otherwise you would have to replicate models, monkey patch search calls which is not good. It would be nice to have APIs and let consumer use that API.
If A needs to get results from B (any model). create API at B end, to return results based on query and content type. Hope this helps Thanks, Harun On Mon, Oct 24, 2011 at 7:07 PM, cec <[email protected]> wrote: > Hi, > > I'have two rails applications, that both use TS to index their models. > > As a new requirement, application A needs to be able to search in > model M of application B. > > After adding to A's database.yml the connection details for the db of > application B and duplicating M, I wonder what is the best approach to > enable searching. > > Do I have to define in A the same index on M that I use in B? > (application A won't modify instance of M, so I don't need any > deltas :) ) > > Is there a way to have TS talk to a different searchd instance when > searching trhough M? > > Thank you! > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/thinking-sphinx?hl=en. > > -- Thanks, Harun @harunpathan -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
