On 11/13/15 10:37 AM, Arun Arora wrote:
Hi Paul,
It sounds interesting :)
Can you give an example…? I didn’t exactly catch the reference of the range as
API arg.
Just pass around a pointer to the message buffer, and use an
offset/length pair to identify each particular value of interest with
On 13/11/15, 9:04 PM, "Dale R. Worley" wrote:
>Arun Arora writes:
>> Is their any specific length of To/ From header defined by the
>> standard (I guess not, but still would like to know other's views)
>
>As far as I can tell, your question is, "Is there a specific length
>defined from To/F
Hi Paul,
It sounds interesting :)
Can you give an example…? I didn’t exactly catch the reference of the range as
API arg.
Thanks,
Arun
On 13/11/15, 8:25 PM, "Paul Kyzivat"
wrote:
>On 11/13/15 6:58 AM, Arun Arora wrote:
>> Hi all,
>>
>> Is their any specific length of To/ From header defi
Arun Arora writes:
> Is their any specific length of To/ From header defined by the
> standard (I guess not, but still would like to know other's views)
As far as I can tell, your question is, "Is there a specific length
defined from To/From headers?" The answer to that is definitely not.
> Cur
On 11/13/15 6:58 AM, Arun Arora wrote:
Hi all,
Is their any specific length of To/ From header defined by the standard (I
guess not, but still would like to know other’s views)
My usual answer to this is that the length of any one header field in
the message is bounded by the size of the mes
I've seen it handled in APIs where the user is required to '\0' terminate the
string. In the event that they don't, it's expected that the application would
crash. Of course, I don't like that approach.
In all honesty, if the user of the API is unable to determine the length of the
strings they
Hmm.. What you say about length is correct and I totally agree with you. I have
also seen rather different lengths, contents of the SIP headers depending upon
the vendor/ implementation and that’s why I wanted to have other’s views on
this.
Also, w.r.t API design and its parameters, I tend to m
Hello,
If you are expecting the user to supply the entirety of the To/From headers,
than the only thing you can do is require the user to provide the length of
each so that you can assign memory storage within your object/function
appropriately. As Brett has said, and I have experienced in the
Hmm.. That’s true, ‘No max should be there’ to support inter-op.
However, for API design, I guess their is no way other than asking API-User to
Provide the length of Strings for To and From.
I am designing the API to receive the To/ From header in form or 'name-addr' or
'addr-spec' in order to
> Is their any specific length of To/ From header defined by the standard
No.
> In case no specific length is defined, is their any common-practice
> for max length?
RFC 3261 section 18.1.1 might provide you some guidance for message size
minimums to support. The common practice is not cap the
Hi all,
Is their any specific length of To/ From header defined by the standard (I
guess not, but still would like to know other’s views)
In case no specific length is defined, is their any common-practice for max
length?
The question is related to the SIP session start API I am working on for
11 matches
Mail list logo
