On a general note, I think 'sequence<Grammar>' in my earlier mail should be replaced with an array Grammar[] to match the recommended way in new web APIs. 2. ... On the other hand it might be annoying to have to respecify the > full list of N grammars every time you just want to change one of them. > Being an array individual elements could be inserted/removed at will just like calling add/remove methods. > **** > > 5. **One question I have, though, is what happens if the actual > grammar at the src uri changes after the Grammar object is created? If the > developer wants to insure that they’re using a completely up to date grammar > do they have always have to remember to create a new Grammar object right > before they add it to the SpeechInputRequest? > Is the concern about the speech service updating the grammar file(s) while a webapp is running in the client machine? I think that is specific to the speech service implementation. - If the grammar is provided by the same speech service, I think when the service updates the grammar data it would also update any in memory caches so any ongoing sessions will continue to work. - If the grammar is provided by someone else and the speech service fetched it over the wire at start of session, it would have caching rules as to how long it would hold a copy before fetching again. Until it fetches again all sessions will continue to use the old grammar data irrespective of whether the client sets a new grammar object or not. -- Cheers Satish
Received on Thursday, 15 September 2011 15:52:26 UTC