Subject: From: Date:

RE: [ECS] ECS -> ACE Dan Hoehnen Sun, 8 Aug 1999 00:22:41 -0400

---

Scott,

First, thanks for the great troubleshooting info.  I'm pretty sure I know
what the problem is.  Change the "aceb:" to "aces:" and it should work.
I know the "aceb:" header is documented, but it's meant for use between ACE
modules.  Please let me know, if you can, where in the documentation you
read to use the "aceb:" header.  I either need to fix the doc's or change
the code to accept "aceb:" from ECS so noone has the same problem.  In
general, you should be able to get by with acec: or aces: when sending
commands from ecs to ace.

Background... When ace gets a command from ecs, it looks for a acec: or
aces: header.  It won't process the message if one of these headers is not
found.  Thus, your problem.  But, if you have the option enabled to forward
all ecs messages to all clients, then the msg is sent to all clients.  This
is what the "TX:192.168.0.1  ACEC:0:ECSM:aceb:waplay:" mesage is.  The
"ECSM" gets added, which tells each client that what follows was a message
from ecs.  Messages from ecs get forwarded to all clients no matter what the
message header is.  That's why you saw it getting sent to the clients.






> -----Original Message-----
> From: Scott Reston [mailto:ih8gates@concentric.net]
> Sent: Saturday, August 07, 1999 6:26 PM
> To: ecs-list@netbloc.com
> Subject: [ECS] ECS -> ACE
>
>
> i'm in the process of evaluating ACE for use with ECS, but i'm
> having a little difficulty getting off of the starting block. for
> those of you using ace: how do you
> send your DDE command to ACE?
>
> for instance. i'm trying to get a basic start/stop of winamp.
> i've got ace server on my ECS machine and ace32 on the winamp
> machine. i can control winamp
> from the server's winamp control console, so i know that ace
> server and ace32 are communicating. ace server is set up to claim
> ID 'A' when communicating
> with ECS. i've set up text items with text of: "aceb:waplay:" and
> "aceb:wastop:". if i set the state of the these items to "send ->
> A", i can see the item in ace's
> network monitor as "TX:192.168.0.1  ACEC:0:ECSM:aceb:waplay:".
> these commands work if i type them directly into the "command to
> server" line on ace's
> network monitor.
>
> is this the correct way to send the command? is it the "ECSM"
> that's causing the command to not 'work' in ace?
>
> thanks in advance...
>
> Scott Reston
> ih8gates@concentric.net
>
>
>
>

---