Re: Kannel WAP-PUSH clarification

Actually, pap and pi are in a way part of Kannel. Tesst_ppg is PI. So
problem here is lack of documentation of *test_ppg*.

Aarno

On 22.5.2005, at 23.27, Alberto Devesa wrote:

> Thomsen,
>
> As I see, you are complaining about something that has nothing to  
> be with
> Kannel documentation. What you need is an open protocol  
> specification (PAP)
> whose scope is totally outside from Kannel.
>
> Take a look at the following URL, specially de Push Access Protocol  
> and
> Service Indication specs:
>
> http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html
>
>
> BTW, I would understand if the Kannel developers feel offended with  
> your
> words. Remember that you get what you pay for and if you don't like  
> just stop
> using it.
>
>
> Alberto
>
>
>
>
> On Sunday 22 May 2005 18:51, Jørgen Thomsen wrote:
>
>> Linkas,
>>
>>
>>> I do agree. Kannel documentation has not been made for unexperienced
>>> people and it needs some backgrounds.
>>>
>>
>> Unexperienced ?? Any system needs an interface description  
>> otherwise it is
>> totally useless.
>>
>> This forum has a lot of people, whose names I find in the relevant  
>> code
>> dated years back, but even if these names also appear in the  
>> documentation,
>> their actual accomplishments there leave something to be desired  
>> in this
>> case. Quoting the first sentence in the user guide "This document  
>> describes
>> how to install and use Kannel,..."
>>
>> I can only say, that most programmers (myself included) find it  
>> much more
>> fun coding new fancy features, but what use are these fancy  
>> features if the
>> programmer is the only one knowing about this ?
>>
>> How about changing the Kannel project, so no new features are  
>> added unless
>> there is also a user guide update accompanying the feature ?
>>
>> Isn't there a wish for the participants to have their work used by  
>> many
>> people ? That can only be accomplished when a product is easy to use.
>>
>>
>>> What I can suggest, after having studied on some sites, is to go  
>>> to the
>>> gateway folder and look for the examples in PHP about SI (Service
>>> Indication) and then you will get it more.
>>>
>>
>> Bad suggestion. There is no PHP-code describing that. If you  
>> search for the
>> term "Service Indication" you will find only 4 lines in the source  
>> files.
>>
>> I managed to deduce one interface as a HTTP POST with a MIME
>> multipart/related part including two parts as the pap and si  
>> documents from
>> the test_ppg code, but that is probably only a partial truth. This  
>> was
>> after wasting several hours, which could have been avoided by a  
>> few lines
>> in the documentation.
>>
>> Thank you, Kannel WAP programmers!
>>
>> I don't volunteer to update the documentation with this because, I  
>> don't
>> know how complete and accurate my newly acquired knowledge is.  
>> Furthermore
>> I find it more appropriate, that the persons actually having  
>> designed the
>> interface finish their work.
>>
>> - Jørgen
>>
>
>
>