Am Donnerstag 07 September 2006 02:22 schrieb Marcel Holtmann: > > > I'll need to read the specs again. But I don't think it's okay to > > > decompose the headers (into ID and TYPE). > > > The TYPE macros on the other hand will be quite useful. > > > > Obex-1.2 spec, ch. 2.1: > > "The low order 6 bits of the header identifier are used to indicate the > > meaning of the header, while the upper 2 bits are used to indicate the > > header encoding." > > > > I called the encodings OBEX_HDR_TYPE_* but the meaning is the same. This > > resolves pretty nice for e.g. the time HI values. > > Note that OBEX_HDR_TYPE_BYTES does not say anything about the format, a > > format ID table would be nice. > > I am not willing to break the API. So only additions are allowed.
That's exactly what it does, extending the API. It does not break it. HS ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
