|
|
sybperl-l Archive
Up Prev Next
From: Michael Peppler <mpeppler at peppler dot org>
Subject: Re: Asychronous communication and Sybperl.
Date: Nov 15 1999 7:47PM
Robert McIlhargie writes:
> Michael Peppler wrote:
>
> > > Robert McIlhargie writes:
>
> > >
> > > I'd be willing to do this. Any hints on where to start? Is it just a matter
> > > of adding XSUB code
> > > for the various CTLib functions?
> >
> > I think that's mostly it, although the boot code (in the initialize()
> > function) sets the NETIO mode before allocating the context. There may
> > need to be a way to allocate alternate contexts, and from there use
> > the asynch options. I haven't really looked into this, though.
> >
>
> How about adding NETIO to one of the supported CON_PROPS so that
> people could just set the NETIO when they do "new Sybase::CTlib ..."? I'll
> start looking into it.
That might work. Just need to point to a different context, and also
make sure that anywhere where 'context' is being used you can refer to
this alternate context instead (although it might be even easier than
that - it's possible that we only refer to the context in a couple of
places.)
Michael
--
Michael Peppler -||- Data Migrations Inc.
mpeppler@peppler.org -||- http://www.mbay.net/~mpeppler
Int. Sybase User Group -||- http://www.isug.com
Sybase on Linux mailing list: ase-linux-list@isug.com
|
