[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Message Etiquette
- Subject: Re: Message Etiquette
- From: "darrenp_lock" <darrenlock@xxxxxxx>
- Date: Mon, 16 Apr 2007 19:56:13 -0000
--5-3497484749-3764116177=:3
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Greg,
thanks for the update. I think I may have come to a few conclusions
and I'll post the proposed schema shortly. However, I do have one
more proposition wrt to the addressing (see inline below)...
Are there any apps out there that apply standard generic processing
of named message blocks. e.g. If I put the folderid or messageid into
the xap message block name are there applications that can extract
this based on simple rules and subsequently call a follow on xap
message to request more details about the message or folder?
Any way, I'll cobble something up as it can always be changed later
[#-o] .
As a side note: are there any plans to introduce schema versions to
allow schemas to evolve over time?
Thanks for the help & advice. Darren.
--- In xAP_developer@xxxxxxx
<mailto:xAP_developer@xxxxxxx> ,
Gregg Liming <gregg@...> wrote:
>
> Quoting darrenp_lock (4/12/07 3:18 AM):
>
> > I hadn't appreciated that a listening
> > port would be created for each logical device. Therefore, I will
> > propose the following format for the Logical Address:
> >
> > DGarage.vxvml.<servername>:.....
> >
> > Now my question here on convention is should the servername be
the
> > Asterisk Server being managed or the servername where the Gateway
is
> > located (the gateway runs on Windows)? The former would allow for
> > multiple Asterisk Servers and probably is more intuitive.
>
> So, if you have multiple asterisk servers that each map to
individual
> values for <servername>, then you'll be creating more than one
logical
> device--right? It's not as though this hasn't been done before--
I've
> personally had to resort to a multi-device approach due to the
original
> limitation on UID subaddressing for gateways w/ large numbers of
known
> or possible endpoints. But, it's not something that I would
personally
> advocate unless it really is essential. If it were me, I'd tend
toward:
>
>
DGarage.vxvml.<servername>:<ast_servername><ast_vmcontext><ast_vmailbo
x>
>
> ... realizing that this makes the canonical endpoint addressing a
bit
> more complex. Limiting support to only one ast server avoids it;
but,
> it also is limiting. (FWIW: I'd be personally interested in using
your
> gw if it does support multiple ast servers).
>
[:-/] As I understand it, I am limited to 254 subaddress IDs, therefore
multiple asterisk servers and contexts will limit the number of
mailboxes somewhat e.g. 2 servers with 2 contexts will limit me to 63
(ish) mailboxes per context per server if I use an address
reservation technique. Unless I just allocate subaddress IDs on a
first come first served basis until I have used all 254 up i.e. max
of 254 mailboxes across any number of servers and contexts?
> > I take your point about the dynamic endpoints in the Sub Address.
I
> > was worried about maintaining the UIDs for the folders &
messages. So
> > I guess I can just address them in the message block. Having a
device
> > for the folder meant commands like DeleteAllMessages could be
applied
> > at the Device level without message block processing. However, if
> > DisplayAllFolders for a MailBox is going to generate a xAP
Message
> > per folder then the context (FolderID) would be in the message
block,
> > so message block processing is going to be required anyway.
> >
> > An example of message block processing required is when the
> > DisplayFolders (for Mailbox) command is executed and a xAP
message is
> > issued per folder indicating the MailBox, FolderName and number
of
> > VMail Messages.
>
> I would assume that Mailbox is an endpoint. Foldername or Folderid
might
> well be embedded in the block name; I think that is preferable to
> embedding into a block property. I'm assuming/hoping that Kevin or
> others will speak up here as well--especially if different or
dissenting
> opinions.
>
> > Ideally, I would like James' HomeSeer Gateway to
> > create and maintain me a HS Device that represents the number of
> > Messages in a particular mailbox folder (as you can guess, I
haven't
> > thought that one through yet!). For info, those devices are then
> > gatewayed out of HS and into MainLobby. An alternative might be
to
> > create a bespoke MainLobby plugin to process my xAP Messages -
> > however, I loose the benenfit of having 'device' information in
HS.
>
> Unfortunately, I have absolutely no useful insight here as I'm not
a HS
> or MainLobby user.
>
--5-3497484749-3764116177=:3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html><body>
<P>Greg,</P>
<P>thanks for the update. I think I may have come to a few
conclusions <BR>and I'll post the proposed schema shortly. However, I
do have one <BR>more proposition wrt to the addressing (see inline
below)...</P>
<P>Are there any apps out there that apply standard generic
processing <BR>of named message blocks. e.g. If I put the folderid or
messageid into <BR>the xap message block name are there applications
that can extract <BR>this based on simple rules and subsequently call
a follow on xap <BR>message to request more details about the message
or folder?</P>
<P>Any way, I'll cobble something up as it can always be changed
later<IMG height="18" alt="#-o" src="http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/34.gif";
width="18">.</P>
<P>As a side note: are there any plans to introduce schema versions
to <BR>allow schemas to evolve over time?</P>
<P>Thanks for the help & advice. Darren.</P>
<P>--- In <A href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A>,
Gregg Liming <gregg@...>
wrote:<BR>><BR>> Quoting darrenp_lock (4/12/07
3:18 AM):<BR>> <BR>> > I hadn't
appreciated that a listening<BR>> > port would be
created for each logical device. Therefore, I will<BR>>
> propose the following format for the Logical
Address:<BR>> > <BR>> >
DGarage.vxvml.<servername>:.....<BR>> >
<BR>> > Now my question here on convention is should
the servername be the<BR>> > Asterisk Server being
managed or the servername where the Gateway <BR>is<BR>>
> located (the gateway runs on Windows)? The former would allow
for<BR>> > multiple Asterisk Servers
and probably is more intuitive.<BR>> <BR>> So, if
you have multiple asterisk servers that each map to
<BR>individual<BR>> values for
<servername>, then you'll be creating more than one
<BR>logical<BR>> device--right? It's not as
though this hasn't been done before--<BR>I've<BR>>
personally had to resort to a multi-device approach due to the
<BR>original<BR>> limitation on UID subaddressing for
gateways w/ large numbers of <BR>known<BR>> or possible
endpoints. But, it's not something that I would
<BR>personally<BR>> advocate unless it really is
essential. If it were me, I'd tend
<BR>toward:<BR>> <BR>>
<BR>DGarage.vxvml.<servername>:<ast_servername><ast_vmcontext><ast_vmailbo<BR>x><BR>>
<BR>> ... realizing
that this makes the canonical endpoint addressing a
<BR>bit<BR>> more complex. Limiting support to
only one ast server avoids it; <BR>but,<BR>> it also is
limiting. (FWIW: I'd be personally interested in using
<BR>your<BR>> gw if it does support multiple ast
servers).<BR>> </P>
<P><IMG height="18" alt=":-/" src="http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/06.gif";
width="18">As I understand it, I am limited to 254 subaddress
IDs, therefore <BR>multiple asterisk servers and contexts will limit
the number of <BR>mailboxes somewhat e.g. 2 servers with 2 contexts
will limit me to 63 <BR>(ish) mailboxes per context per server if I
use an address <BR>reservation technique. Unless I just allocate
subaddress IDs on a <BR>first come first served basis until I have
used all 254 up i.e. max <BR>of 254 mailboxes across any number of
servers and contexts?</P>
<P><BR>> > I take your point about the dynamic
endpoints in the Sub Address. <BR>I<BR>> > was
worried about maintaining the UIDs for the folders &
<BR>messages. So<BR>> > I guess I can just
address them in the message block. Having a
<BR>device<BR>> > for the folder meant commands
like DeleteAllMessages could be <BR>applied<BR>>
> at the Device level without message block processing. However,
if<BR>> > DisplayAllFolders for a MailBox is going to
generate a xAP Message<BR>> > per folder then the
context (FolderID) would be in the message
<BR>block,<BR>> > so message block processing is
going to be required anyway.<BR>> > <BR>>
> An example of message block processing required is when
the<BR>> > DisplayFolders (for Mailbox) command is
executed and a x
AP <BR>message is<BR>> > issued per folder
indicating the MailBox, FolderName and number of<BR>> >
VMail Messages.<BR>> <BR>> I would assume that
Mailbox is an endpoint. Foldername or Folderid
<BR>might<BR>> well be embedded in the block name; I
think that is preferable to<BR>> embedding into a block
property. I'm assuming/hoping that Kevin or<BR>>
others will speak up here as well--especially if different or
<BR>dissenting<BR>> opinions.<BR>>
<BR>> > Ideally, I would like James' HomeSeer Gateway
to<BR>> > create and maintain me a HS Device that
represents the number of<BR>> > Messages in a
particular mailbox folder (as you can guess, I
<BR>haven't<BR>> > thought that one through
yet!). For info, those devices are then<BR>> >
gatewayed out of HS an
d into MainLobby. An alternative might be to<BR>> >
create a bespoke MainLobby plugin to process my xAP Messages
-<BR>> > however, I loose the benenfit of having
'device' information in <BR>HS.<BR>> <BR>>
Unfortunately, I have absolutely no useful insight here as I'm not
<BR>a HS<BR>> or MainLobby
user.<BR>><BR></P>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=1820/stime=1176764378";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br><br>
<div style="width:500px; text-align:right; margin-bottom:1px;
color:#909090;">
<tt>SPONSORED LINKS</tt>
</div>
<table bgcolor=#e0ecee cellspacing="13"
cellpadding="0" width=500px>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjYjN0azFtBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3NjQzNzg-?t=ms&k=Filemaker+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Sql+server+developer&w4=Web+developer&w5=Php+developer&c=5&s=108&g=0&.sig=aGwzOHWoMXeq_43Jix8FKQ";>Filemaker
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjYmVhamdoBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3NjQzNzg-?t=ms&k=Sql+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Sql+server+developer&w4=Web+developer&w5=Php+developer&c=5&s=108&g=0&.sig=KdkJ37xcz6o6aKyju4GPuQ";>Sql
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjcGVyaThzBF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3NjQzNzg-?t=ms&k=Sql+server+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Sql+server+developer&w4=Web+developer&w5=Php+developer&c=5&s=108&g=0&.sig=Y2Cl41GpJD04dk8vnjhH2A";>Sql
server developer</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjY2gwNHBkBF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3NjQzNzg-?t=ms&k=Web+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Sql+server+developer&w4=Web+developer&w5=Php+developer&c=5&s=108&g=0&.sig=61LAoCeyEhDkBGB767LsxQ";>Web
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjcG1sZTk4BF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3NjQzNzg-?t=ms&k=Php+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Sql+server+developer&w4=Web+developer&w5=Php+developer&c=5&s=108&g=0&.sig=8S56dAWPuzOmElm54L8LeA";>Php
developer</a></tt>
</td>
</tr>
</table>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xAP_developer/join;_ylc=X3oDMTJmdXFkbHZwBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzExNzY3NjQzNzg-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkZG1kbzZuBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMTc2NzY0Mzc4";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</body></html>
--5-3497484749-3764116177=:3--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|
![http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/34.gif"](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/34.gif"){kind=link}
![http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/06.gif"](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/06.gif"){kind=link}