Summary: | TpClientChannelFactory should cache and re-use existing TpChannel | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
Component: | tp-glib | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | 38142 | ||
Bug Blocks: |
Description
Guillaume Desmottes
2011-06-06 01:32:38 UTC
I would make TpChannel instances unique per factory instances. So one could still create its own factory that create other subclasses for the same channel. Now for the how to implement this, I'm not sure it's nice to do code in interfaces. Maybe we need a TpBaseProxyFactory and make TpAutomaticProxyFactory and TpBasicProxyFactory subclasses of it? (In reply to comment #2) > Maybe we need a TpBaseProxyFactory and make TpAutomaticProxyFactory > and TpBasicProxyFactory subclasses of it? We can't without breaking ABI, I think. We could just add a _ensure_channel() (falling back to _create_channel() in the iface if not implemented) and let factories implementing it. Closing as dup of bug #38142 since it replaces TpClientChannelFactory completely *** This bug has been marked as a duplicate of bug 38142 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.