TABLE action using database lookup – separate process?

This topic has 1 reply, 2 voices, and was last updated 9 years, 9 months ago by James Cobane.

Creator

Topic
January 21, 2016 at 5:07 pm #54961
Peter Heggie
Participant
If we use a TABLE action in a translator and the table is a database lookup, must this translator run in its own process? Or can we have multiple route details under a route, in an inbound thread, and multiple route details can call this same translator?

Peter Heggie
PeterHeggie@crouse.org
Creator

Topic

Viewing 0 reply threads

Author

Replies
- January 21, 2016 at 7:20 pm #83619
  James Cobane
  Participant
  Peter,
  
  Based on the documentation, there is no indication that you need to run each xlate in its own process when using a database with the table lookup. I would think that the table lookup using a database could be implemented the same as a normal table lookup within an xlate, and allow multiple routes within the same process to use the same (or different) xlate(s).
  
  Otherwise trying to manage routing/processes based on use of databases for table lookups would be a bit challenging.
  
  Jim Cobane
  
  Henry Ford Health
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.