Hi Biruntha, 1. What is the reason us to provide the support for "query_sm", most of the SMSC does not provide the support for this. I wonder we ever need to support it.
2. When we maintain the SMPP session in the pool, we have to manage the idle sessions. We need to send "enquire_link" periodically, otherwise the SMSC will terminate the session, after few minutes of idle time. So you may need to implement a custom pool implementation. Cheers, Ruwan On Tue, Nov 22, 2016 at 3:04 PM, Biruntha Gnaneswaran <[email protected]> wrote: > yes Malaka, i'm considering that also. > > Biruntha > > Associate Software Engineer > WSO2 > Email : [email protected] > Linkedin : https://lk.linkedin.com/in/biruntha > Mobile : +94773718986 > > On Tue, Nov 22, 2016 at 2:39 PM, Malaka Silva <[email protected]> wrote: > >> Hi Biruntha, >> >> There can be multiple gateways based on client configuration and for >> multiple tenants. >> We need to reuse only the sessions for the given service provider and >> tenant. >> I guess you are considering those as well? >> >> On Tue, Nov 22, 2016 at 12:14 PM, Biruntha Gnaneswaran <[email protected] >> > wrote: >> >>> Hi All, >>> >>> Currently i’m working on the SMPP connector improvement as described >>> below: >>> >>> 1. >>> >>> Query the status of the submitted message :- When message is send >>> using the SMPP protocol, SMSC returns a message reference (messageId). >>> Then >>> we are able to query the SMSC for the delivery status of this message. >>> 2. >>> >>> Maintain the SMPP session between multiple calls of send SMS >>> operation :- Current version of the connector creates new session for >>> each >>> sms. To solve this problem, i create own connection pool to use it in the >>> multithreading environment by creating a ConcurrentLinkedQueue and push >>> the >>> connections to that queue. Each time a thread requests a connection, >>> connection is popped out from queue. Once job is done, threads push >>> connection back to queue. If there are no connection in the queue, it >>> will >>> create a new connection. >>> >>> >>> This improvement is regarding the jira [1] and [2]. >>> >>> [1] https://wso2.org/jira/browse/ESBCONNECT-120 >>> >>> [2] https://wso2.org/jira/browse/ESBCONNECT-121 >>> >>> Thanks, >>> Biruntha >>> >>> Associate Software Engineer >>> WSO2 >>> Email : [email protected] >>> Linkedin : https://lk.linkedin.com/in/biruntha >>> Mobile : +94773718986 >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Technical Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> https://wso2.com/signature >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Ruwan Abeykoon* *Associate Director/Architect**,* *WSO2, Inc. http://wso2.com <https://wso2.com/signature> * *lean.enterprise.middleware.*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
