On 01/03/2012, at 09:44 AM, Terry Judd wrote:
Thanks - I'll give that a go.
Sent from my iPhone
On 01/03/2012, at 9:14 AM, "Bjoernke von Gierke"
mailto:b...@mac.com>> wrote:
Preferences -> Composing -> Increase quote level
(just below "Quote the text of the original message")
On 29.02.2012,
Thanks - I'll give that a go.
Sent from my iPhone
On 01/03/2012, at 9:14 AM, "Bjoernke von Gierke" wrote:
> Preferences -> Composing -> Increase quote level
>
> (just below "Quote the text of the original message")
>
>
> On 29.02.2012, at 23:01, Terry Judd wrote:
>
>> You can probably blame
Preferences -> Composing -> Increase quote level
(just below "Quote the text of the original message")
On 29.02.2012, at 23:01, Terry Judd wrote:
> You can probably blame Apple mail for that.
>
> Terry...
>
> Sent from my iPhone
>
> On 01/03/2012, at 8:46 AM, "Bob Sneidar" wrote:
>
>> Not
You can probably blame Apple mail for that.
Terry...
Sent from my iPhone
On 01/03/2012, at 8:46 AM, "Bob Sneidar" wrote:
> Not to be too critical, but it is nearly impossible for me to read this as a
> thread when prior conversations are not "quoted" in some way to distinguish
> them from th
Not to be too critical, but it is nearly impossible for me to read this as a
thread when prior conversations are not "quoted" in some way to distinguish
them from the actual post. My mind gives up trying.
Bob
On Feb 29, 2012, at 11:25 AM, Terry Judd wrote:
>
> On 01/03/2012, at 12:19 AM, Da
On 01/03/2012, at 12:19 AM, Dave Cragg wrote:
On 29 Feb 2012, at 09:49, Terry Judd wrote:
Hi guys - we have a reasonably complex Livecode app that makes lots of server
requests - typically initiated by posting data to php routines on a secure
(https) server. Generally things work well but oc
On 29/02/2012, at 11:33 PM, Bjoernke von Gierke wrote:
If you're using libURL, then that one should close the sockets for you, and
amassing of unclosed sockets would be a bug in there. On the other hand, if you
made the sockets yourself from scratch, they're not closed (note that the
remote ho
On 29 Feb 2012, at 09:49, Terry Judd wrote:
> Hi guys - we have a reasonably complex Livecode app that makes lots of server
> requests - typically initiated by posting data to php routines on a secure
> (https) server. Generally things work well but occasionally things go awry
> and we start
I'm pretty sure that sockets do not close themselves automatically. "the
socketTimeoutInterval" (and "the socketTimeout" message) is weirdly named, in
that it doesn't do anything beyond tell you that time has passed, and does not
actually act or closes anything. It just repeats infinitely, as lo
Hi guys - we have a reasonably complex Livecode app that makes lots of server
requests - typically initiated by posting data to php routines on a secure
(https) server. Generally things work well but occasionally things go awry and
we start seeing slowdowns and odd errors (including the dreaded
10 matches
Mail list logo