[Bug 39644] add custom properties to file transfers

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Nov 2 01:35:47 CET 2011


https://bugs.freedesktop.org/show_bug.cgi?id=39644

--- Comment #6 from Daniele E. Domenichelli <daniele.domenichelli at gmail.com> 2011-11-01 17:35:47 PDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > Is it possible to add, for example, a method provideMetadata (for the sender)
> > and a method acceptMetadata (for the receiver) to get more flexibility?
> > These methods should be able to transfer an RDF/XML string...
> 
> I don't quite understand what you're after here. You want to send more than one
> batch of metadata alongside a file transfer? Could you explain the use case
> here a little more? As it is, the sender provides metadata when they create the
> FT channel, and the recipient receives it when they receive the offer. Is this
> insufficient?

My use case is this:

In kde-telepathy we want to transfer metadata that we get from nepomuk together
with the file, but we want to keep as simple as possible sending a file from a
program, therefore the program should just choose the file and the target.
The handler is then started and it should check the services supported by the
other side and eventually, if "nepomuk metadata" are supported, add metadata to
the file transfer.

The metadata is stored in triples that can be related to the file (i.e.
"Filename" "Author is" "John") but also not related direcly to the file (i.e.
"John" "email address is" "john at foo.com)
We want to be able to choose which metadata is transferred or to avoid sending
them to someone from some external configuration dialog. Moreover nepomuk could
be disabled and in this case no metadata should be sent.
Including this into a library is in my opinion redundant (we want to link
directly to Telepathy-Qt4), and therefore it should be handled by the handler
once it receives the channel.

Our plan (that I also started to implement) was to add a stream tube service
and when the handler receives a file transfer channel and the state changes to
accepted, if the other side supports that service, open a streamtube, transfer
the metadata and when the channel is closed send the real file.
Since you are implementing this interface, I think that something like this
could be supported directly by telepathy...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.



More information about the telepathy-bugs mailing list