I'd have to double check all the sql used for registration, but I doubt memcache is expressive enough to act as the registration store. For instance, you can't get a list of registrations from it (sofia status profile internal).
memcache is a keystore only. That being said, one could use memcache as a umm.. well cache like it is designed as a front end to the real odbc database. Consult memcache first then hit the db. Doing anything like that would require moving much of mod_memcache up into core, something I promised I would do at one point but never got around to doing -- lack of time and motivation and no strong use case IMO. On Thu, Nov 19, 2009 at 4:23 AM, Lon Baker <[email protected]> wrote: > If we could access mod_memcache for registration information that > would be ideal and highly robust, since you can share memcache with > external applications. > > Lon > > On Thu, Nov 19, 2009 at 2:07 AM, Leon de Rooij <[email protected]> > wrote: >> Well, you can of course easily have a loadbalancer with failover in front of >> your sql servers and have them replicate to each other. Freeswitch will >> reconnect if a connection goes down. Perhaps failover is also possible >> directly through odbc ? Does anyone know if that's possible ? >> regards, >> Leon >> >> >> On Nov 19, 2009, at 10:33 AM, jay binks wrote: >> >> I believe OBDC is the official way.. >> however id love look at doing this in a higher performance way, without the >> single point of failure.. >> local memcache, in front of OBDC or something ?? >> not 100% sure of it, but just using a single central database is a little >> bit of a concern in a carrier environment. >> Jay >> >> >> On Thu, Nov 19, 2009 at 7:14 PM, Leon de Rooij <[email protected]> >> wrote: >>> >>> Hi, >>> >>> Not that I know of, but you can use odbc to store registrations and >>> share it that way.. >>> >>> regards, >>> >>> Leon >>> >>> On Nov 19, 2009, at 9:40 AM, Woody Dickson wrote: >>> >>> > Hi, >>> > >>> > Is there anyway to store registration info in memcache instead of >>> > sqlite? >>> > >>> > By doing that, it is possible for multiple freeswitch to share the >>> > same user registration info. >>> > >>> > Is there anyway I can intercept the registration success/failure >>> > event and write stuff to memcache myself? >>> > >>> > thanks, >>> > woody >>> > _______________________________________________ >>> > FreeSWITCH-users mailing list >>> > [email protected] >>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >>> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >>> > http://www.freeswitch.org >>> >>> >>> _______________________________________________ >>> FreeSWITCH-users mailing list >>> [email protected] >>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >>> http://www.freeswitch.org >> >> >> >> -- >> Sincerely >> >> Jay >> _______________________________________________ >> FreeSWITCH-users mailing list >> [email protected] >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> >> _______________________________________________ >> FreeSWITCH-users mailing list >> [email protected] >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> > > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > -- -Rupa _______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
