Hello Experts, Is there any possibility of using a different XML-RPC engine that does not involve HTTP ? The reason being, there are a few XML engines out there that avoids the HTTP overhead, TCP setup-teardown, & also uses very minimal resources Best regards, Abdul Hakeem
you can optimize the traffic by using XML-RPC only for directory entries, so that it's only used for user registration events. And the rest could be done through the ESL interface. Also I'm not sure, probably XML-RPC can support HTTP keepalive connections? need to look at the sources for that... On Thu, Aug 27, 2015 at 2:14 PM, Abdul Hakeem <alhakeem@gmail.com> wrote:
Hello Experts,
Is there any possibility of using a different XML-RPC engine that does not involve HTTP ? The reason being, there are a few XML engines out there that avoids the HTTP overhead, TCP setup-teardown, & also uses very minimal resources Best regards, Abdul Hakeem
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
HTTP overhead isn't that bad (and ESL has a similar format doesn't it?). I'd be surprised and interested to hear what the scenario is where HTTP is adding significant load. But to avoid TCP setup/teardown, slap on e.g. nginx and turn on keepalives. That should get you most of the way there. -Michael -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Abdul Hakeem Sent: Thursday, August 27, 2015 6:14 AM To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] XML RPC Hello Experts, Is there any possibility of using a different XML-RPC engine that does not involve HTTP ? The reason being, there are a few XML engines out there that avoids the HTTP overhead, TCP setup-teardown, & also uses very minimal resources Best regards, Abdul Hakeem _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Abdul Hakeem
-
Michael Giagnocavo
-
Stanislav Sinyagin