I think your points are well taken and I certainly do not want to start down a road that is a dead end. What makes me think I "need" VXML is that is what my client is requesting. That is usually a pretty good determination in my book. That being said I am not beyond pushing another solution if I think it will be to their benefit. I am not looking for input on the project design. I am trying to determine if there would be benefit to Freeswitch of having a built in VXML interpreter. That is my only real question. If not, I will push much harder on the client to reconsider their request and consider other alternatives.
what makes you think you "need" voicexml,I wouldnt suggest flooding the market with yet another half done voicexml interpreter...if you try to implement one from scratch, you will quickly realize that finishing the last 10% is more than 90% of the work. Then its in the state as all the other opensource voicexml interpreters out there.what you end up with just kinda smells like voicexml, and isnt terribly portable.. then you might be asking yourself why didnt i just use some other scripting language in FS and save myself all that time.VoiceXML from my experience is an all or nothing thing. People either want it, or they dont.They dont want a half-baked interperter that cant pass the IR compliance suite.I dont know how we can offer if it makes sense in the "design of the project you are working on".. you havent offered much detail there.
_______________________________________________
Freeswitch-dev mailing list
Freeswitch-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org