All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: Update interface with variable port numbers?
Date: Wed, 12 Jan 2011 07:57:51 -0800	[thread overview]
Message-ID: <1294847871.3873.76.camel@aeonflux> (raw)
In-Reply-To: <4D2D5F61.5040404@stericsson.com>

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

Hi Jessica,

> we could probably use an update in the push_notification_register_agent
> in plugins/push-notification.c so that it would be possible to specify 
> port numbers instead of them being hardcoded with
> 
> #define WAP_PUSH_SRC_PORT 9200
> #define WAP_PUSH_DST_PORT 2948
> 
> We would like to be able to use the
> oma-ilp		7276/tcp    OMA Internal Location Protocol
> 
> specified on
> http://www.iana.org/assignments/port-numbers
> 
> This could also be used for other WAP based services.
> 
> Is this something that you would agree would be useful and we could add 
> to the TODO list?

what is the content of these messages? For WAP Push it is clearly
defined. Are these also WAP Push PDUs?

Regards

Marcel



      reply	other threads:[~2011-01-12 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12  7:59 Update interface with variable port numbers? Jessica Nilsson
2011-01-12 15:57 ` Marcel Holtmann [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=1294847871.3873.76.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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.