Hey, I am new to XMPP and new to event based(Asynchronous) programming , hence I need guidance in structuring my XMPP based application.
We are building a real time location based service where XMPP forms the communications framework. The plan is to use pubsub functionality to get the geolocation from various users. The business data, including co-ordinates is persisted in MySQL database. The business logic layer connects to the XMPP server as a Component. One of the tasks of the business logic component is also to store the data in the database. *Here's the question* - Should I have to structure my business logic application using Twisted to take the advantage of the concurrent connection capability of XMPP? To put the question in other words, if I design my business logic on django framework, which is a synchronous framework, will it create bottle neck for rest of the system? If django doesn't work efficiently, should I use Twisted to build my business logic component? Forgive my noob-ness in the question. As mentioned earlier, this is my first foray into XMPP and event based programming. Any suggestions on general architecture to build components for XMPP based applications are most welcome. regards, andy
_______________________________________________ Twisted-Jabber mailing list [email protected] https://mailman.ik.nu/mailman/listinfo/twisted-jabber
