Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 19 of 19 total
Thread ServerProcedure
Thu, Apr 19 2012 6:30 PMPermanent Link

Steve Gill

Avatar

Hi Phil,

<< If not I'll have to look into using Indy (ahhhh). >>

If you are using RAD Studio XE2 then you also get a full version of IP*Works, which you can download from your EDN account.  

I have been using it with the IP Multicasting protocol to send messages between client applications and a server so that's another option you could look at besides UDP or TCP/IP.

Steve
Fri, Apr 20 2012 1:44 AMPermanent Link

IQA

Thanks Roy and Steve for your suggestions.

I'm using C++ Builder XE (not had the need to move to XE2 for now) so I can't get IP*Works and I'm not sure about Synapse as I've never used them and I'm trying to steer away from any learning curve. But I will if the Messaging doesn't appear in the next version.

It's just nice if I cant keep it all under one roof so to speak. One less thing to have to worry about and keep updated / implemented in future versions of the this project.

Thanks again,

Phil.
Tue, Apr 24 2012 11:01 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Phil,

<< I'm wondering if I should be looking at an alternative way to get a
message layer happening between a client / server or should I just hold in
there for the Messaging layer for general messaging notifications and
broadcasts with the ElevateDB server? >>

Just to confirm - are you talking about the user-defined request handling in
the EDB Server like DBISAM has, or the async messaging and notifications ?
I'm assuming it's the latter, but you recently asked about the former, so
I'm just making sure. Smile

--
Tim Young
Elevate Software
www.elevatesoft.com
Tue, Apr 24 2012 6:45 PMPermanent Link

IQA

<< Just to confirm - are you talking about the user-defined request handling in
the EDB Server like DBISAM has, or the async messaging and notifications ?
I'm assuming it's the latter, but you recently asked about the former, so
I'm just making sure. Smile
>>

Sorry Tim, I got in a muddle, I'm still refering to the Server Procedure so my client and server applications can communicate like the following example using DBISAM...

void __fastcall TMainForm::ServerEngineServerProcedure(TObject *Sender,
     TDBISAMSession *ServerSession, const AnsiString ProcedureName)
{
 int LicenseCommand;

 if (AnsiCompareText(ProcedureName,"LicenseProcedure") == 0)
 {
   LicenseCommand = ServerSession->RemoteParams->ParamByName("LicenseCommand")->AsInteger;
   ServerSession->RemoteParams->Clear();

etc etc  ............
Wed, Apr 25 2012 1:49 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Philip,

<< Sorry Tim, I got in a muddle, I'm still refering to the Server Procedure
so my client and server applications can communicate like the following
example using DBISAM... >>

Good, because that's easy, whereas the notification stuff isn't so easy. Wink

--
Tim Young
Elevate Software
www.elevatesoft.com
Mon, May 7 2012 12:54 AMPermanent Link

IQA

Cool thanks Tim, glad it was the easier one to do Wink



On 26/04/2012 3:49 AM, Tim Young [Elevate Software] wrote:
> Philip,
>
> << Sorry Tim, I got in a muddle, I'm still refering to the Server
> Procedure so my client and server applications can communicate like the
> following example using DBISAM... >>
>
> Good, because that's easy, whereas the notification stuff isn't so easy.
> Wink
>
Wed, May 23 2012 8:30 PMPermanent Link

IQA

Hi Tim,

I just wanted to touch base and see if we are any closer to having the
Server Procedure equivelant in ElevateDB...

I'm Currently moving a 2nd software product from DBISAM over to
ElevateDB so in effect we will be upgrading all our customers who these
products from DBISAM to ElevateDB and they are both client / server
products and use the Server Procedure for some time critical features to
import external data from PABX phone systems as dictated by the client
program.

Any news would be helpful,

Thanks again,

Phil.


On 26/04/2012 3:49 AM, Tim Young [Elevate Software] wrote:
> Philip,
>
> << Sorry Tim, I got in a muddle, I'm still refering to the Server
> Procedure so my client and server applications can communicate like the
> following example using DBISAM... >>
>
> Good, because that's easy, whereas the notification stuff isn't so easy.
> Wink
>
Wed, Jun 20 2012 11:59 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Phil,

<< I just wanted to touch base and see if we are any closer to having the
Server Procedure equivelant in ElevateDB... >>

Yep, it's done (and has been done for a while now), and I should be able to
roll out a new minor release for EDB soon.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Jun 29 2012 3:34 AMPermanent Link

Kong Aw

"Tim Young [Elevate Software]" wrote:


Yep, it's done (and has been done for a while now), and I should be able to
roll out a new minor release for EDB soon.

That is great news.  

KK Aw
« Previous PagePage 2 of 2
Jump to Page:  1 2
Image