may be a bug？

[cc_developer]

I have tried libdlna-0.2.3 with ushare-1.1a ,but it did not work when i use xbmc playing media on the DMS.
So i changed the "dlna_info" in file profiles.c,and it works .
Below is the patch file.
  ---------------------------------------------------

diff -urN libdlna-0.2.3/src/profiles.c libdlna/src/profiles.c
-- libdlna-0.2.3/src/profiles.c 2007-11-27 04:47:43.000000000 +0800
+++ libdlna/src/profiles.c 2011-04-01 21:58:08.507491000 +0800
@@ -435,10 +435,10 @@
   strcat (protocol, p->mime);
   strcat (protocol, ":");
  
-  sprintf (dlna_info, "%s=%d;%s=%d;%s=%.2x;%s=%s;%s=%.8x%.24x",
-           "DLNA.ORG_PS", speed, "DLNA.ORG_CI", ci,
-           "DLNA.ORG_OP", op, "DLNA.ORG_PN", p->id,
-           "DLNA.ORG_FLAGS", flags, 0);
+  sprintf(dlna_info, "%s=%s;%s=%.2x;%s=%d;%s=%d;%s=%.8x%.24x",
+       "DLNA.ORG_PN", p->id, "DLNA.ORG_OP", op,
+       "DLNA.ORG_PS", speed,"DLNA.ORG_CI", ci,
+       "DLNA.ORG_FLAGS", flags, 0);
   strcat (protocol, dlna_info);

   return strdup (protocol);

[cc_developer]

By the way, i read the DLNA_Interoperability_Guidelines_v1.0 , and it says that "the relative order of pn-param, op-param, ps-param, and *(other-param) used in 4th_field is mandatory"  in section 7.3.11 (MM DIDL-Lite protocolInfo values: 4th Field).  

Also in DLNA Guidelines_v1.5 , it says that "Note: In all guidelines that relate to the syntax of the 4th field, the relative order of pn-param,op-param, ps-param, ci-param, flags-param, and *(other-param) used in 4th_field is mandatory. For example, pn-param cannot appear after op-param, psparam,ci-param, flags-param, or *(other-params)." in section 7.3.30( MM protocolInfo values: 4th Field   Requirement ).

so i think the order should follow the standards.

[cc_developer]

hope it helps!