From: dlzc on
Dear JD:

On Apr 26, 8:48 am, JD <jdh...(a)ig.com.br> wrote:
> Hi Geoff,
>
> Environment:
>
> - LAN
> - Domain
> - Server with static IP
> - Others PC dynamic
> - my app should receive/send the messages.
>
> Thanks.

What happens if you have a simple shared database, that has four
fields, message ID, expires date, target code, and a memo field with
the message?

Then you can periodically poll for changes in this database... and
post changes as required?

David A. Smith
From: JD on
Using RegisterTimer, right? But I think it would turn my app slow.
From: Geoff Schaller on
David.

Understood, but nor is such an approach appropriate. The correct answer
is to build a service which manages such things and interface it with
Active Directory.

If the AD route is too complex then just a simple NT service would do.

Geoff


"dlzc" <dlzc1(a)cox.net> wrote in message
news:3a1c89d7-fb87-4a28-8507-6c133d05ec9d(a)w32g2000prc.googlegroups.com:

> Dear Geoff Schaller:
>
> On Apr 26, 12:44 am, "Geoff Schaller"
> <geo...(a)softxwareobjectives.com.au>
> wrote:
>
> > It has been replaced with msg.exe
>
>
> It is even uglier than that:
> http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/952dbd19-54d1-466d-a817-59918dc41d57
>
> In mixed OS LANs, MSG.exe does not talk to XPs "NET SEND". Not
> whining, the OP hasn't said if this would be a problem.
>
> David A. Smith

From: Geoff Schaller on
No - why do you say this?

"JD" <jdhora(a)ig.com.br> wrote in message
news:1ef1f00c-2b78-44f6-a9ad-926bba3d63e2(a)o15g2000vbb.googlegroups.com:

> Using RegisterTimer, right? But I think it would turn my app slow.

From: Geoff Schaller on
Jairo.

But what you are saying is that you wish your client application to
provide server level features??? That usually is not the role of a
client application and if you are unwilling to use the operating system
for this purpose then there really only two options:

1. As David suggests - a polled database solution
2. you write a service

Personally I would go with the database option because it is simplest to
implement and distribute but it is tied 100% to your application
running. A service is more universal and could now operate to users even
when they don't run the app.

Cheers,

Geoff



"JD" <jdhora(a)ig.com.br> wrote in message
news:ebd94e2c-270c-41d1-8e90-a643329e7803(a)v14g2000yqb.googlegroups.com:

> Hi Geoff,
>
> Environment:
>
> - LAN
> - Domain
> - Server with static IP
> - Others PC dynamic
> - my app should receive/send the messages.
>
> Thanks.
>
> Jairo.