<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-size: 10pt;">>I would build it this way:<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">><br>>1) Design the dialplan logically so it is understandable and maintainable.<br>><br>>2) Code up the AGIs in whatever language you are comfortable. I would use <br>>C, but that's what I'm most comfortable with.<br>><br>>3) Confirm everything works like you think it should.<br>><br>>4) Measure to identify where the real bottlenecks are.<br>><br>>5) Attack the top 1 or 2 bottlenecks. The solution may be:<br>><br>>a) Recode an AGI in C.<br>><br>>b) Re-implement an AGI as fastagi() on the same server.<br>><br>>c) Re-implement an AGI
as fastagi() on another server.<br>><br>>6) Go to step 3<br><br>Can FastAGI call FastAGI? The application needs to contact another FastAGI server written in Java to lookup various billing information.<br><br><br><br></div></div></div><br>
</body></html>