[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: Message Etiquette
------=_NextPart_000_003E_01C780C4.2A9E9610
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_003F_01C780C4.2A9E9610"
------=_NextPart_001_003F_01C780C4.2A9E9610
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Gregg,
sorry I noticed that I keep dropping the extra 'g' off your name in the
pos=
ts=20
Hopefully you are used to it the same way I am to people adding an
unnecess=
ary e to my surname I.e. Locke instead of Lock
Rgds, Darren.
----- Original Message -----=20
From: Gregg Liming=20
To: xAP_developer@xxxxxxx=20
Sent: Tuesday, April 17, 2007 4:04 AM
Subject: Re: [xAP_developer] Re: Message Etiquette
Hi Darren,
Quoting darrenp_lock (4/16/07 3:56 PM):
> 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?
Well, I can only speak emphatically about misterhouse; and, it
definitely can. I would guess other apps can as certain schemas would
seem to encourage this. I would hope that you will get additional
pros/cons from others, however, before making assumptions.
> As a side note: are there any plans to introduce schema versions to
> allow schemas to evolve over time?
I'll defer to others "in the know". It would seem more useful if
this
were the case. In practice, I see more "embellishment" (i.e.,
additions
or refinements to interpretation) than strict schema control. There are
certain occasions/situations where this leads to considerable problems.
> :-/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?
Those assumptions seem quite valid. I would suggest considering several
points: (1) the xAP schema is either close or has adopted the extended
addressing capability that would make this constrain moot (although,
there seems to be an unending series of issues getting things moving
here), (2) I have personally used your "first-come-first-served"
concept--realizing that my personal approach results in some only
semi-persistent UID allocation (yet nothing broke despite concerns that
might suggest otherwise if exceptionally conservative) and (3) be very,
very practical about what you think are your real environments (e.g.,
reasonable # of servers, contexts, etc) are as planning for the worst
case can lead to an exceptional and often inappropriate level of effort
(which is fine--so long as "worst case" really deserves that
level of
attention). If I were to have adopted the full spirit and constraint of
the original UID subaddressing limit, I would have bailed on xAP long ago=
.
Regards,
Gregg
=20=20=20
------=_NextPart_001_003F_01C780C4.2A9E9610
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type
content=text/html;charset=iso-8859-1><!-- Network content -->
<META content="MSHTML 6.00.6000.16397"
name=GENERATOR></HEAD>
<BODY id=MailContainerBody
style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; FONT-SIZE: 10pt;
COLOR: #000000; PADDING-TOP: 15px; FONT-FAMILY: Arial; BACKGROUND-COLOR:
#ffffff"
bgColor=#ffffff leftMargin=0 topMargin=0 CanvasTabStop="true"
acc_role="text"
name="Compose message area">
<DIV>Gregg,</DIV>
<DIV> </DIV>
<DIV>sorry I noticed that I keep dropping the extra 'g' off your name
in the
posts <IMG title="Embarrassed smile emoticon"
style="FLOAT: none; MARGIN: 0px; POSITION: static" tabIndex=-1
alt="Embarrassed smile emoticon"
src="cid:E996CE6F2E67463D8B9827E73C5878A3@Office"
MSNNonUserImageOrEmoticon="true"></DIV>
<DIV> </DIV>
<DIV>Hopefully you are used to it the same way I am to people adding
an
unnecessary e to my surname I.e. Locke instead of Lock</DIV>
<DIV> </DIV>
<DIV>Rgds, Darren.</DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message -----
</DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color:
black"><B>From:</B>
<A title=mailto:gregg@xxxxxxx href="mailto:gregg@xxxxxxx";>Gregg
Liming</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=mailto:xAP_developer@xxxxxxx
href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B>
Tuesday, April 17, 2007 4:04
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B>
Re: [xAP_developer] Re: Message
Etiquette</DIV>
<DIV><BR></DIV>
<DIV id=ygrp-text>
<P>Hi Darren,<BR><BR>Quoting darrenp_lock (4/16/07 3:56
PM):<BR><BR>> 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?<BR><BR>Well,
I can only
speak emphatically about misterhouse; and, it<BR>definitely can. I
would guess
other apps can as certain schemas would<BR>seem to encourage this. I
would
hope that you will get additional<BR>pros/cons from others, however,
before
making assumptions.<BR><BR>> As a side note: are there
any plans to
introduce schema versions to<BR>> allow schemas to evolve over
time?<BR><BR>I'll defer to others "in the know". It
would seem more useful if
this<BR>were the case. In practice, I see more
"embellishment" (i.e.,
additions<BR>or refinements to interpretation) than strict schema
control.
There are<BR>certain occasions/situation<WBR>s where this leads
to
considerable problems.<BR><BR>> :-/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?<BR><BR>Those assumptions seem quite valid. I would
suggest
considering several<BR>points: (1) the xAP schema is either close or
has
adopted the extended<BR>addressing capability that would make this
constrain
moot (although,<BR>there seems to be an unending series of issues
getting
things moving<BR>here), (2) I have personally used your
"first-come-<WBR>first-served"<BR>concept--realizing
that my personal approach
results in some only<BR>semi-persistent UID allocation (yet nothing
broke
despite concerns that<BR>might suggest otherwise if exceptionally
conservative) and (3) be very,<BR>very practical about what you think
are your
real environments (e.g.,<BR>reasonable # of servers, contexts, etc)
are as
planning for the worst<BR>case can lead to an exceptional and often
inappropriate level of effort<BR>(which is fine--so long as
"worst case"
really deserves that level of<BR>attention). If I were to have
adopted the
full spirit and constraint of<BR>the original UID subaddressing
limit, I would
have bailed on xAP long
ago.<BR><BR>Regards,<BR><BR>Gregg<BR><BR></P></DIV><!--End
group email --></BLOCKQUOTE>
<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=1822/stime=1176799767";
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=X3oDMTJjdTJ0NHZmBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3OTk3Njc-?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=X3oDMTJjZWxzb3AxBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3OTk3Njc-?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=X3oDMTJjajkxYjdsBF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3OTk3Njc-?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=X3oDMTJjdWk5dmk4BF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3OTk3Njc-?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=X3oDMTJjbWhkcDRsBF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTYyOTQ3NgRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNzY3OTk3Njc-?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=X3oDMTJmcW01ZTR2BF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzExNzY3OTk3Njc-";>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=X3oDMTJkbmpudDdzBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMTc2Nzk5NzY3";>
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>
------=_NextPart_001_003F_01C780C4.2A9E9610--
------=_NextPart_000_003E_01C780C4.2A9E9610
Content-Type: image/gif;
name="Emoticon8.gif"
Content-Transfer-Encoding: base64
Content-ID: <E996CE6F2E67463D8B9827E73C5878A3@Office>
R0lGODlhEwATALMPAP3mS/fy5OyyLeG7bfKUM/JlNfXJOejMirCIMdmmKppuKMqZL8Wwi7maYFMf
DQAAACH5BAEAAA8ALAAAAAATABMAAASp8Enm3Dm1tiC71IYBjMBSMZynHCLpKsKQPsEhKC9Oximr
ODpFADgKJQ40g5AIWBJDgkVNOQwGqoCQ4TigBqxXhUFATjTIBIVupIYR3m9E4l0guLKFfJ2QQJDz
di4Gent9A3SBJIN6bwsNNm8tRQKIcShoklqUcAsISAcJAkptMAJzBAIIDBIBAwmaZLFkCBsdraGy
sX21HjULC7gJfaozHjQHDQjKDSjGEQA7
------=_NextPart_000_003E_01C780C4.2A9E9610--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|