Re: more oddities with xapintranet.ocx

["rleong1" <reynold@xxxxxxxxxxxxxxxxxxxx>]

thanks!  that helped me find the problem.  i downloaded the latest
viewer and looked at the hex view.  i realized i had a space after the
"{" and "}" in the messages i was creating and that was
causing it not
to work.  not sure why the same apps on a different machine would be
able to see the messages though.

--- In xap_automation@xxxxxxx, Kevin Hawkins
<yahoogroupskh@...> wrote:
>
> ?Hi, can you compare the original message and the second one in
Viewers
> hex view.  Are they absolutely identical ?  What about the Wireshark
> comparison ?
> Which version xAP hub are you running ?
>
> K
>
>  rleong1 wrote:
> >
> > thanks for your reply. i did close everything and started them up
> > again and i'm still having the same problem.
> >
> > --- In xap_automation@xxxxxxx
> > <mailto:xap_automation%40yahoogroups.com>,
"turner228" <kevin@> wrote:
> > >
> > > Hi
> > > I have seen similar behaviour before on a couple of
occasions on the
> > > system I have been developing on.
> > >
> > > It seemed to be due to the frequent stopping and starting of
an app
> > > when I was testing and trying stuff out
> > >
> > > Shutting down **all** xAP apps and xAP services, then
restarting
them
> > > resolved this for me
> > >
> > > HTH
> > > Kevin T
> > >
> > > --- In xap_automation@xxxxxxx
> > <mailto:xap_automation%40yahoogroups.com>,
"rleong1" <reynold@> wrote:
> > > >
> > > > i'm building an app using 1.4 of the ocx. it's working
fine
capturing
> > > > messages but when i try to send xap messages, the other
apps
on the
> > > > same machine cannot see the message. the same apps on a
different
> > > > machine will see it.
> > > >
> > > > for example, i'll send message.display from it and
intranet
launcher
> > > > on the same machine won't see it. the message viewer on
the same
> > > > machine will see it. if i replay it from the viewer,
launcher
will see
> > > > it. launcher on a different machine will see the
original
message as
> > > > well. i grabbed wireshark captures.
> > > >
> > >
> >
> >
>



------------------------------------