So last night I'm trying to use couriertls for an application outside of
the normal courier mechanisms. Initially, things went great.
However, I quickly ran into a problem, which I spent altogether far too
long debugging - couriertls does not do "normal" name resolution. By
that I mean it does not
Jon Nelson wrote:
So last night I'm trying to use couriertls for an application outside of
the normal courier mechanisms. Initially, things went great.
However, I quickly ran into a problem, which I spent altogether far too
long debugging - couriertls does not do "normal" name resolution. By
that
On Tue, 25 Nov 2003, Andrew Newton wrote:
> Jon Nelson wrote:
> > So last night I'm trying to use couriertls for an application outside of
> > the normal courier mechanisms. Initially, things went great.
> > However, I quickly ran into a problem, which I spent altogether far too
> > long debuggin
On Tue, 25 Nov 2003, Andrew Newton wrote:
> Jon Nelson wrote:
> > So last night I'm trying to use couriertls for an application outside of
> > the normal courier mechanisms. Initially, things went great.
> > However, I quickly ran into a problem, which I spent altogether far too
> > long debuggin
Jon Nelson wrote:
On Tue, 25 Nov 2003, Andrew Newton wrote:
Er, oops. I saw that you put section 5 in there.
I misspoke earlier.
What I mean to ask is this: "what does this have to do with couriertls,
and more importantly, what does this have to do with the parts of
courier that have *nothing* to
