did you see my other email on this thread with the xml macro idea?<br>When it comes to displacing the complexity there are many choices.<br><br>if you want to make some api call that can look in xml and generate a big | sep dial string that's entirely possible.<br>
you could do something similar with lua or some other embedded language as well.<br><br><br><div class="gmail_quote">On Wed, Aug 26, 2009 at 12:48 PM, Carlos S. Antunes <span dir="ltr"><<a href="mailto:csa@nowthor.com">csa@nowthor.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Anthony Minessale wrote:<br>
> Unfortunately it's still a problem because the core bridge/originate<br>
> mechanism does not parse XML it's only parses the dial string markup.<br>
<br>
</div>Wouldn't it be possible to "translate" the markup to a dial string prior<br>
to hitting the core mechanism?<br>
<div class="im"><br>
> In the end you must end up with one string of application and one<br>
> string of data.<br>
><br>
<br>
</div>How about something like<br>
<br>
<action application="bridge"><data> ... </data></action><br>
<br>
being somewhat* equivalent to<br>
<br>
<action application="bridge" data=" ... ">?<br>
<br>
(* somewhat to be properly define later)<br>
<div class="im"><br>
> I am very strict about maintaining scope boundaries between abstract<br>
> concepts. I think it's the number 1 breakdown that led to asterisk<br>
> getting so messed up over the years and I want to avoid that same plague.<br>
<br>
</div>I totally agree with you on this.<br>
<div class="im"><br>
> I hope you understand and if you want to continue to ponder some more<br>
> functionality I welcome it.<br>
<br>
</div>Don't worry, I rarely stop having ideas. Feel free to shoot them down at<br>
will! :)<br>
<font color="#888888"><br>
Carlos<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>