URLs can easily be a few KB, especially if they involve URL-encoded non-ASCII characters. I'm personally not a fan of any limit for handle length in the spec; I think that any length we give is fairly arbitrary and will come back to bite us.
S.
-----Original Message-----
From: Gil Tayar [mailto:]
Sent: Thursday, September 19, 2002 4:01 AM
To:
Subject: RE: [wsrp-wsia] [I#92] Maximum size of a handle
As long as it's SHOULD and not MUST, it is OK, but anyway the 128 number is
too small. Our current implementation uses a URL as the "entityHandle" (a la
Web philosophy), and URL-s can approach 128. A 1K-4K minimum (SHOULD, not
MUST) would be logical to me.
Gil
-----Original Message-----
From: Gil Tayar [mailto:]
Sent: Thu, September 19, 2002 08:40
To:
Subject: [wsrp-wsia] [I#92] Maximum size of a handle
Topic: interface
Class: Minor Technical
Title: Maximum size of a handle
Document Section: throughout
Description:
Current draft spec just says that a handle is a string. For reasons of
efficient processing, it would be useful to limit the length of the handle
to something reasonable. Considering that an entityHandle SHOULD encode the
consumerHandle when Consumer side persitence is used and that a refHandle
encodes an entityHandle and a sessionHandle, the length should not be too
small. Suggestion = 128 characters.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Discussion:
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
