[standards-jig] JIDs (JEP-0029)
dave at dave.tj
Mon Apr 29 21:03:01 UTC 2002
Well, what currently happens if somebody tries to use a resource of that lenght? Do the behaviors of JINC's and our servers differ?
Dave Cohen <dave at dave.tj>
> Bytes instead of characters because it is much easier to check for.
> UTF-8 will allow is 1 byte, 2 byte, 3 byte, 4 byte, and 5 byte
> (including header byte) characters. I don't want everybody to have to
> necessarily have to fully validate the encoding just to verify correct #
> of characters. Let the parser take care of validation.
> Two solid technical reasons for limiting resource:
> 1) In order to perform JID manipulations safely, one cannot use stack
> space if there is no limit. This forces temporary calculations onto the
> heap which is just stupid in terms of cost.
> 2) As a fixed length character field, it is more database schema
> friendly. If I can have Hume's _Treatise of Human Nature_ as my
> resource, then the only way you can store that w/out truncating it is to
> store it as a BLOB or CLOB. Try searching that efficiently!
> Thomas Muldowney wrote:
> >I would personally like to see a note about why we want to limit
> >resources to 256 bytes. Is there a solid technical reason? Also, why
> >256 bytes? Would it also be more beneficial to replace all references
> >to bytes with characters, since we should not be speaking in storage
> >On Mon, 2002-04-29 at 11:00, Peter Saint-Andre wrote:
> >>Craig Kaes has submitted a JEP that seeks to fully define what a Jabber
> >>Identifier is. Note that this JEP includes changes to some of the current
> >>(implementation-specific) features of JIDs, such as the fact that right
> >>now there is no limit on the length of a resource. You can review the JEP
> >>Peter Saint-Andre
> >>email+jabber: stpeter at jabber.org
> >>weblog: http://www.saint-andre.com/blog/
> >>Standards-JIG mailing list
> >>Standards-JIG at jabber.org
> >Standards-JIG mailing list
> >Standards-JIG at jabber.org
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards