metadata dbus
Hi,
Does the getting of metadata is supported now in the bluez .
Signature · 2 lines
Thanks& Regards, Sathish N
Luiz Augusto von Dentz
maintainerHi Sathish,
Quoted 6 lines · sathish
Hi,
Does the getting of metadata is supported now in the bluez .--
Thanks& Regards,
Sathish N
Currently not, but it should not be too much effort to get it done since we have already implemented the protocol layer.
Signature · 1 line
Luiz Augusto von Dentz
Quoted 12 lines · Luiz Augusto von Dentz
Hi Sathish,
Quoted 6 lines · sathish
Hi,
Does the getting of metadata is supported now in the bluez .--
Thanks& Regards,
Sathish NCurrently not, but it should not be too much effort to get it done since we have already implemented the protocol layer.
Hi Luiz,
The bluez that is in git repository has the dbus api saying
something about metadata information , will that dbus api will be useful
Signature · 7 lines
Thanks& Regards, Sathish N -- Thanks& Regards, Sathish N
Luiz Augusto von Dentz
maintainerHi Sathish,
Quoted 3 lines · sathish
Hi Luiz,
The bluez that is in git repository has the dbus api saying something about metadata information , will that dbus api will be useful
I suppose you are talking about org.bluez.MediaPlayer? This interface is implemented by other processes (players) to expose their metadata, IMO it is not really suitable for the opposite role. I would suggest having another interface specific for this role (e.g. org.bluez.Target or org.bluez.Player) which gonna be registered in the device object path, it should be pretty similar to MediaPlayer interface except for Release. It also a good idea to think about how we gonna address multiple players since that is supported in AVRCP 1.4.
Signature · 1 line
Luiz Augusto von Dentz
Quoted 6 lines · Luiz Augusto von Dentz
Hi Sathish,
Quoted 3 lines · sathish
Hi Luiz,
The bluez that is in git repository has the dbus api saying something
about metadata information , will that dbus api will be useful
Quoted 9 lines
I suppose you are talking about org.bluez.MediaPlayer? This interface is implemented by other processes (players) to expose their metadata, IMO it is not really suitable for the opposite role. I would suggest having another interface specific for this role (e.g. org.bluez.Target or org.bluez.Player) which gonna be registered in the device object path, it should be pretty similar to MediaPlayer interface except for Release. It also a good idea to think about how we gonna address multiple players since that is supported in AVRCP 1.4.
Hi Luiz,
Thanks for the kind reply. Will these interface gives metadata
information about all players or players that support mpris.
Signature · 2 lines
Thanks& Regards, Sathish N
FTP file authorization and transfer progress support
In reply to sathishHi,
Currently in OBEXD, only OPP put has authorization and file progress indication. I am planning to implement the same in FTP put/get/delete the same way as it does in OPP. But application may need to know the type of the obex operation to which the Authorize method is invoked. So I am planning to add a new method namely GetProperties in transfer, which returns the type of the operation (put/get/delete) so that application can use it in Authorize method. Please let me know your suggestions.
Thanks and Regards
Jaganath
Re: FTP file authorization and transfer progress support
Hi Jaganath,
Quoted 7 lines · Jaganath
Currently in OBEXD, only OPP put has authorization and file progress indication. I am planning to implement the same in FTP put/get/delete the same way as it does in OPP. But application may need to know the type of the obex operation to which the Authorize method is invoked. So I am planning to add a new method namely GetProperties in transfer, which returns the type of the operation (put/get/delete) so that application can use it in Authorize method. Please let me know your suggestions.
We try to avoid such extra round-trips in our D-Bus APIs. If such a feature is really needed the essential context information should be provided as parameters to the "authorize" call.
Johan
Luiz Augusto von Dentz
maintainerRe: FTP file authorization and transfer progress support
Hi Jaganath,
Quoted 11 lines · Johan Hedberg
Hi Jaganath,
Quoted 7 lines · Jaganath
Currently in OBEXD, only OPP put has authorization and file progress indication. I am planning to implement the same in FTP put/get/delete the same way as it does in OPP. But application may need to know the type of the obex operation to which the Authorize method is invoked. So I am planning to add a new method namely GetProperties in transfer, which returns the type of the operation (put/get/delete) so that application can use it in Authorize method. Please let me know your suggestions.
Quoted 3 lines
We try to avoid such extra round-trips in our D-Bus APIs. If such a feature is really needed the essential context information should be provided as parameters to the "authorize" call.
Im not so sure authorize here is really useful since FTP requires connection authorization anyway, we can create transfers if the purpose is to log them.
Signature · 1 line
Luiz Augusto von Dentz
Re: FTP file authorization and transfer progress support
Hi Johan and Luiz
--------------------------------------------------
From: "Luiz Augusto von Dentz" <[email protected]>
Sent: Tuesday, November 29, 2011 7:46 PM
To: "Jaganath" <[email protected]>; <[email protected]>
Subject: Re: FTP file authorization and transfer progress support
Quoted 14 lines
Hi Jaganath,
Quoted 11 lines · Johan Hedberg
Hi Jaganath,
Quoted 7 lines · Jaganath
Currently in OBEXD, only OPP put has authorization and file progress indication. I am planning to implement the same in FTP put/get/delete the same way as it does in OPP. But application may need to know the type of the obex operation to which the Authorize method is invoked. So I am planning to add a new method namely GetProperties in transfer, which returns the type of the operation (put/get/delete) so that application can use it in Authorize method. Please let me know your suggestions.
Quoted 7 lines
Quoted 3 lines
We try to avoid such extra round-trips in our D-Bus APIs. If such a feature is really needed the essential context information should be provided as parameters to the "authorize" call.
Im not so sure authorize here is really useful since FTP requires connection authorization anyway, we can create transfers if the purpose is to log them.
Thanks for your reply.
Even if FTP has connection authorization I think it is better to ask file authorization for put/get/delete. This gives more flexibility to application. It is up to application to decide whether to ask end user or simply accept. Also in put case if a file with same filename is already there, then this approach will be useful for application to handle that.
Re: FTP file authorization and transfer progress support
Hi Jaganath,
Quoted 25 lines · Jaganath
From: "Luiz Augusto von Dentz" <[email protected]>
Quoted 16 lines
Quoted 14 lines · Johan Hedberg
Quoted 12 lines · Jaganath
Currently in OBEXD, only OPP put has authorization and file progress indication. I am planning to implement the same in FTP put/get/delete the
same way as it does in OPP. But application may need to know the type of the
obex operation to which the Authorize method is invoked. So I am planning to
add a new method namely GetProperties in transfer, which returns the type of
the operation (put/get/delete) so that application can use it in Authorize
method. Please let me know your suggestions.Quoted 7 lines
Quoted 3 lines
We try to avoid such extra round-trips in our D-Bus APIs. If such a feature is really needed the essential context information should be provided as parameters to the "authorize" call.
Im not so sure authorize here is really useful since FTP requires connection authorization anyway, we can create transfers if the purpose is to log them.
Quoted 6 lines
Thanks for your reply.
Even if FTP has connection authorization I think it is better to ask file authorization for put/get/delete. This gives more flexibility to application. It is up to application to decide whether to ask end user or simply accept. Also in put case if a file with same filename is already there, then this approach will be useful for application to handle that.
I think you may be confusing use cases.
If you are an FTP server, you are giving authorized remote users blanket authority to read, write or browse, or some combination, your exposed FTP file system. I suppose you could require additional operation-by-operation request/confirm, but that would quickly make the system very clumsy. It's not the usage model that FTP was designed for.
That is why we have the OPP profile, which is specifically for single object sharing, and that has that kind of request/confirm model.
Signature · 4 lines
Brian Gix [email protected] Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
Re: FTP file authorization and transfer progress support
Am Mittwoch, 30. November 2011, 07:45:49 schrieb Brian Gix:
Quoted 3 lines
If you are an FTP server, you are giving authorized remote users blanket authority to read, write or browse, or some combination, your exposed FTP file system.
You could add OBEX authentication support for access control.
HS