Well, I would suggest using both a robot and a gadget. The robot might be able to do the text to speech conversion and save the speech in the datastore where then the gadget retrieves it and outputs it to the user. I have not fully looked at the gadget API so I am not sure if this is even possible, but it would be better to have the robot do to conversion because then the work is not done client side, lagging the already lagging wave. At the same time, GAE, where the robot is hosted, only allows certain quotas on CPU time and such and having so much text to speech conversions happening at once might make the robot exceed those limits. I would really say it is a matter of perspective.
On Sat, Sep 5, 2009 at 4:04 PM, maxsap <[email protected]> wrote: > > Hello all I would like to build a text to speech application, my > current thoughts are to build a robot or a gadget and set a separate > servet to let it do the TTS and then send back to a wave user the > result. I actually have two questions , the first is if it is possible > to use sip to make a session and send data (voice) and second I > haven't really decide which is better for this project a robot or a > gadget? > thanks in advanced maxsap > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
