From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] test-ussd becomes send-ussd
Date: Mon, 09 Jul 2012 11:52:12 -0500 [thread overview]
Message-ID: <4FFB0C3C.8010906@gmail.com> (raw)
In-Reply-To: <1341851969.16443.0.camel@aeonflux>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Hi Marcel,
On 07/09/2012 11:39 AM, Marcel Holtmann wrote:
> Hi Denis,
>
>>> ---
>>> test/send-ussd | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> test/test-ussd | 75 --------------------------------------------------------
>>> 2 files changed, 75 insertions(+), 75 deletions(-)
>>> create mode 100755 test/send-ussd
>>> delete mode 100755 test/test-ussd
>>>
>>
>> Why don't we just get rid of test-ussd and create a new send-ussd script
>> that doesn't do any stdin handling. Something along the lines of:
>>
>> ss.GetProperties()
>>
>> if state == 'idle'
>> rsp = ss.Initiate()
>> elif state == 'user-response'
>> rsp = ss.Respond()
>>
>> print response
>>
>> And perhaps another ussd related script that just cancels the request.
>> Would this satisfy your requirements?
>
> are the existing test/initiate-ussd and test/cancel-ussd not good
> enough?
>
initiate-ussd is close but not quite, it doesn't handle network
initiated USSDs.
Anyway, the point here is that we need to get rid of test-ussd, it
really serves no purpose.
Regards,
-Denis
prev parent reply other threads:[~2012-07-09 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 15:45 [PATCH 1/2] test-ussd becomes send-ussd Philippe Nunes
2012-07-02 15:45 ` [PATCH 2/2] test-ussd: new script more generic Philippe Nunes
2012-07-09 16:26 ` [PATCH 1/2] test-ussd becomes send-ussd Denis Kenzior
2012-07-09 16:39 ` Marcel Holtmann
2012-07-09 16:52 ` Denis Kenzior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFB0C3C.8010906@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.