Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

PB 8 COM/MTS Troubles

3 posts in Objects Last posting was on 2003-01-19 15:28:18.0Z
Justin Posted on 2002-10-30 10:52:39.0Z
Newsgroups: sybase.public.powerbuilder.objects
From: "Justin" <nospam@my-inbox.thanks>
Subject: PB 8 COM/MTS Troubles
Date: Wed, 30 Oct 2002 10:52:39 -0000
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: pc3-swin2-4-cust56.oxf.cable.ntl.com 80.7.151.56
Message-ID: <364_ZAPfhRAgCHA.296@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.powerbuilder.objects:831
Article PK: 713393

Hi,

I have been putting a MTS/COM distributed application together using
PB8.0.2, Windows 2000 Server with COM+ and developing on 2000 / XP Pro.

After a lot of trial and error, I am at the point where the application is
working in as much as I can instantiate the server-side component from a
client, call functions on it and pass data between the client and the
component.

Now I have a problem with the way the component is actually running. The
plan when I started was to instantiate the component the first time a client
(or other component) requested its services and then hold it in an active
state for a finite period of time so that any other clients would be able to
connect to it and use its data. The behaviour I'm seeing now, is that every
client effectively creates its own instance of the component and therefore
the benefits of using cached data are lost.

Also, the application model I've designed so far has server-side components
talking to each other, again with a view to caching and sharing data but
this too appears to create seperate instances instead of using the one that
may already be running.

I suspect this is down to the threading model, instantiation methods or
application configuration, but so far I've only been confused by the
documentation I've read on the web and in the Powerhelp on-line books, which
actually give very little useable information about COM/MTS beyond the
theory.

Has anyone else been through this already and found a practical method of
making it work ?

Any advice would be most gratefully received.

Regards,
Justin
justin@<r-e-m-o-v-e-t-h-i-s>energisetechnology.co.uk


Adrian Gomez Posted on 2002-11-22 03:43:15.0Z
Newsgroups: sybase.public.powerbuilder.objects
From: "Adrian Gomez" <adriancgomez@hotmail.com>
Subject: Re: PB 8 COM/MTS Troubles
Date: Fri, 22 Nov 2002 00:43:15 -0300
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: host206.200-43-39.telecom.net.ar 200.43.39.206
Message-ID: <364_9l2yRudkCHA.309@forums.sybase.com>
References: <364_ZAPfhRAgCHA.296@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.powerbuilder.objects:749
Article PK: 713318

I am currently facing the same situation and could'nt find any documentation
or help.
I couldn't find out how to:
1) Access a COM component already instantiated from client (just like you do
on EAServer with shared components).
2) Keep an instance alive and running as a service component with methods
like run, start and stop and sending it to "sleep" every X seconds. (I
believe this feature is not supported on MTS)

I just had to modify my apps architecture (not very funny) because of this.

"Justin" <nospam@my-inbox.thanks> wrote in message
news:ZAPfhRAgCHA.296@forums.sybase.com...
> Hi,
>
> I have been putting a MTS/COM distributed application together using
> PB8.0.2, Windows 2000 Server with COM+ and developing on 2000 / XP Pro.
>
> After a lot of trial and error, I am at the point where the application is
> working in as much as I can instantiate the server-side component from a
> client, call functions on it and pass data between the client and the
> component.
>
> Now I have a problem with the way the component is actually running. The
> plan when I started was to instantiate the component the first time a
client
> (or other component) requested its services and then hold it in an active
> state for a finite period of time so that any other clients would be able
to
> connect to it and use its data. The behaviour I'm seeing now, is that
every
> client effectively creates its own instance of the component and therefore
> the benefits of using cached data are lost.
>
> Also, the application model I've designed so far has server-side
components
> talking to each other, again with a view to caching and sharing data but
> this too appears to create seperate instances instead of using the one
that
> may already be running.
>
> I suspect this is down to the threading model, instantiation methods or
> application configuration, but so far I've only been confused by the
> documentation I've read on the web and in the Powerhelp on-line books,
which
> actually give very little useable information about COM/MTS beyond the
> theory.
>
> Has anyone else been through this already and found a practical method of
> making it work ?
>
> Any advice would be most gratefully received.
>
> Regards,
> Justin
> justin@<r-e-m-o-v-e-t-h-i-s>energisetechnology.co.uk
>
>


Alex Posted on 2003-01-19 15:28:18.0Z
Newsgroups: sybase.public.powerbuilder.objects
Date: Sun, 19 Jan 2003 17:28:18 +0200
From: Alex <alex@silverbyte.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: PB 8 COM/MTS Troubles
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 64
NNTP-Posting-Host: bzq-117-238-199.cust.bezeqint.net 192.117.238.199
Message-ID: <364_$0Y5pL9vCHA.198@forums.sybase.com>
References: <364_ZAPfhRAgCHA.296@forums.sybase.com> <364_9l2yRudkCHA.309@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.powerbuilder.objects:170
Article PK: 712747

http://my.sybase.com/detail?id=47853

Adrian Gomez wrote:
> I am currently facing the same situation and could'nt find any documentation
> or help.
> I couldn't find out how to:
> 1) Access a COM component already instantiated from client (just like you do
> on EAServer with shared components).
> 2) Keep an instance alive and running as a service component with methods
> like run, start and stop and sending it to "sleep" every X seconds. (I
> believe this feature is not supported on MTS)
>
> I just had to modify my apps architecture (not very funny) because of this.
>
> "Justin" <nospam@my-inbox.thanks> wrote in message
> news:ZAPfhRAgCHA.296@forums.sybase.com...
>
>>Hi,
>>
>>I have been putting a MTS/COM distributed application together using
>>PB8.0.2, Windows 2000 Server with COM+ and developing on 2000 / XP Pro.
>>
>>After a lot of trial and error, I am at the point where the application is
>>working in as much as I can instantiate the server-side component from a
>>client, call functions on it and pass data between the client and the
>>component.
>>
>>Now I have a problem with the way the component is actually running. The
>>plan when I started was to instantiate the component the first time a
>
> client
>
>>(or other component) requested its services and then hold it in an active
>>state for a finite period of time so that any other clients would be able
>
> to
>
>>connect to it and use its data. The behaviour I'm seeing now, is that
>
> every
>
>>client effectively creates its own instance of the component and therefore
>>the benefits of using cached data are lost.
>>
>>Also, the application model I've designed so far has server-side
>
> components
>
>>talking to each other, again with a view to caching and sharing data but
>>this too appears to create seperate instances instead of using the one
>
> that
>
>>may already be running.
>>
>>I suspect this is down to the threading model, instantiation methods or
>>application configuration, but so far I've only been confused by the
>>documentation I've read on the web and in the Powerhelp on-line books,
>
> which
>
>>actually give very little useable information about COM/MTS beyond the
>>theory.
>>
>>Has anyone else been through this already and found a practical method of
>>making it work ?
>>
>>Any advice would be most gratefully received.
>>
>>Regards,
>>Justin
>>justin@<r-e-m-o-v-e-t-h-i-s>energisetechnology.co.uk
>>
>>
>
>
>