Hi!
Possible error?
Looking at the PBAP Specification P.27
"5.3.3 Name
This header specifies the name of the folder to be retrieved. The
value shall not include
any path information, since the PullvCardListing function uses
relative paths. An empty
name header may be sent to retrieve the folder that is the current directory."
and then in the backend implementations:
/plugins/phonebook-tracker.c
/plugins/phonebook-ebook.c
both use absolute paths in the implementation of:
phonebook_create_cache(const char *name, phonebook_entry_cb entry_cb,
phonebook_cache_ready_cb ready_cb, void *user_data, int *err)
Is there something in PBAP Core I've missed?
I looked for concats of the current_folder but it seems to pass the
information to the implementation raw.
//Anders Wid?n
On Fri, Nov 25, 2011 at 3:49 PM, Anders Widen <[email protected]> wrote:
> Hi!
>
> Possible error?
>
> Looking at the PBAP Specification P.27
>
> "5.3.3 Name
> This header specifies the name of the folder to be retrieved. The
> value shall not include
> any path information, since the PullvCardListing function uses
> relative paths. An empty
> name header may be sent to retrieve the folder that is the current directory."
>
> and then in the backend implementations:
> /plugins/phonebook-tracker.c
> /plugins/phonebook-ebook.c
>
> both use absolute paths in the implementation of:
>
> phonebook_create_cache(const char *name, phonebook_entry_cb entry_cb,
> ? ? ?phonebook_cache_ready_cb ready_cb, void *user_data, int *err)
>
>
> Is there something in PBAP Core I've missed?
> I looked for concats of the current_folder but it seems to pass the
> information to the implementation raw.
I guess path is generated in pbap_get(). There is type comparison for
VCARDLISTING_TYPE and then the stored name is built from current path
and given name.
--
Slawomir Bochenski