Return-Path: From: "Liu, Raymond" To: Marcel Holtmann CC: "linux-bluetooth@vger.kernel.org" Date: Mon, 24 Nov 2008 13:48:10 +0800 Subject: RE: Can we change org.openobex.Client's dbus node path? Message-ID: <0463F45F3606F4428ED35AC8C709F92E0217AB09@pdsmsx502.ccr.corp.intel.com> References: <0463F45F3606F4428ED35AC8C709F92E0217A981@pdsmsx502.ccr.corp.intel.com> <0463F45F3606F4428ED35AC8C709F92E0217AA44@pdsmsx502.ccr.corp.intel.com> <0463F45F3606F4428ED35AC8C709F92E0217AAF9@pdsmsx502.ccr.corp.intel.com> In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E0217AAF9@pdsmsx502.ccr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 List-ID: > > I found the reason. During interface register object_path_unref did call Sorry, typo here: should be object_path_ref >invalidate_parent_data. But for our case: we have path "/" at first, and w= e >register interface at "/org/openobex/Session0", there are no data for >"/org/openobex", so no any parent introspect data is invalidated. But the = whole >/org/openobex path is created for the first time. So actually the "/"'s >introspect data need to be invalidated.