Open Source Telephony
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [SMS D-Bus 02/19] sms: introduce message ID API
Date: Thu, 05 Aug 2010 11:37:51 -0700	[thread overview]
Message-ID: <1281033471.19261.108.camel@localhost.localdomain> (raw)
In-Reply-To: <4C5B0127.8050703@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]

On Thu, 2010-08-05 at 13:21 -0500, Denis Kenzior wrote: 
> Hi Inaky,
> 
> On 08/05/2010 01:07 PM, Inaky Perez-Gonzalez wrote:
> > On Thu, 2010-08-05 at 13:02 -0500, Denis Kenzior wrote: 
> >> Hi Inaky,
> >>
> >>>> The current message id is 32 bits.  Why are we stopping at 16?  We could
> >>>> go all the way to 64 if needed...
> >>>
> >>> Well, at the end what gets sent to the network is 16 bits right?
> >>
> >> So I think we're all confused here.  This ID is not being sent to the
> >> network.  It is only used for uniquely identifying the message over
> >> D-Bus and to message history.  This number can be as small or as big as
> >> we want.
> > 
> > I was under the impression that you wanted to use this for the ref also,
> > and thus it is imprinted into the PDUs by set_ref_and_to(). Can you
> > confirm this?
> > 
> 
> No, you're totally confused ;)  Ref is only sent on messages that are
> multi-fragment.  It is not used for single-fragment messages.  The logic
> is currently implemented per spec and I never had the intention to do it
> any other way.

Okay, so then this means that all the current ref infrastructure
(monotonically increased) is left in place and the message ID stuff is
used only internally for D-Bus and whichever other needs there are. I'll
up it to 64-bits.

> > Ok, I see your concern. Proper seeding of the RNG should take care of
> > that case, but either way works. If you want hashing + time() seeding
> > that can be done easily.
> > 
> > I still could use clarification on which other fields of the 'struct
> > sms' union you want to have hashed other than the PDU payloads.
> > 
> 
> All of them.  Again, it might be much simpler to do this over the
> fragments when they are in true PDU form.  This can be done in
> sms_assembly and tx_queue_entry_new since they deal with fragments already.
> 
> Alternatively handling the individual structure fields can be done as well.

I'll look into it.




  reply	other threads:[~2010-08-05 18:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 23:50 [SMS D-Bus 00/19] pull request Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 01/19] write_file: make transaction-safe Inaky Perez-Gonzalez
2010-08-05 17:03   ` Denis Kenzior
2010-08-03 23:50 ` [SMS D-Bus 02/19] sms: introduce message ID API Inaky Perez-Gonzalez
2010-08-05 17:10   ` Denis Kenzior
2010-08-05 17:18     ` Inaky Perez-Gonzalez
2010-08-05 18:02       ` Denis Kenzior
2010-08-05 18:07         ` Inaky Perez-Gonzalez
2010-08-05 18:21           ` Denis Kenzior
2010-08-05 18:37             ` Inaky Perez-Gonzalez [this message]
2010-08-05 23:34             ` Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 03/19] sms: implement SHA256-based message IDs [incomplete] Inaky Perez-Gonzalez
2010-08-05 17:20   ` Denis Kenzior
2010-08-05 18:17     ` Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 04/19] sms: document the org.ofono.SmsMessage interface Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 05/19] sms: document handle_sms_status_report() Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 06/19] struct tx_queue_entry: add a destructor Inaky Perez-Gonzalez
2010-08-05 17:04   ` Denis Kenzior
2010-08-03 23:50 ` [SMS D-Bus 07/19] sms: introduce bare state machine and transitions Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 08/19] sms: introduce the Wait-for-Status-Report state Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 09/19] sms: introduce a state change callback for messages Inaky Perez-Gonzalez
2010-08-03 23:50 ` [SMS D-Bus 10/19] sms: export outgoing messages over D-Bus Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 11/19] sms: send PropertyChanged signals on state change Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 12/19] sms: introduce sms_msg_cancel and its D-Bus wrapper Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 13/19] sms: Implement D-Bus SMS-MSG::GetProperties Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 14/19] sms: document SMS Message's D-Bus 'To' property Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 15/19] sms: test code for message's D-Bus GetProperties Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 16/19] automake: fix generation of symlinks for headers Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 17/19] sms: document variable usage in sms_msg_send() Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 18/19] sms: add test case for message cancel Inaky Perez-Gonzalez
2010-08-03 23:51 ` [SMS D-Bus 19/19] sms: add test case for state change signals Inaky Perez-Gonzalez

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=1281033471.19261.108.camel@localhost.localdomain \
    --to=inaky@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox