Thank you for the help. This is great information that the Doc people might want to
include in the Docs, especially the parts about the name being required and the type
not working at all.
I noticed something else recently, that the count field doesn't get transmitted
either. I put a count of 1 on the send in the socket structure, and a count of 0 comes
out on the receiving end in the socket structure. Is that true, or am I possibly doing
something wrong?
Shannon
>The name field should always be filled in with an extension that can be
>used to identify your data. Name should be considered a required field. If
>no name is given, the system will give your data the name "Palm.exg". The
>reason that Name is so important is that on non-palm systems - like
>windows, name is the only field recognized. If you beam your data to a
>windows machine, it must have a filename. If you receive data from a
>windows machine, it will only have a filename.
>
>The built in apps support the following filename extensions:
>.txt -- memopad
>.vcf -- address book
>.vcs -- datebook and todo
>.prc,pdb,.pqa --- Launcher
>
>The type field is not currently transmitted over IrOBEX when you beam data.
>So the type field will always end up as NULL on the receiving device. The
>built in applications do not currently register for any types. These are a
>bugs that should be fixed in some future PalmOS release. The correct thing
>to do is to send both type and file information. The type field should
>contain standard MIME types for data.
>
>If you specify a creator, the creator will take priority over the other
>settings. Creator will only work between two palm devices. In general you
>only need to use creator if you want to force data to go to a particular
>application.
>
>--- Gavin
>
>
> >Sent by: Shannon <[EMAIL PROTECTED]>
> >
> >
> >To: "Palm Developer Forum" <[EMAIL PROTECTED]>
> >cc: (Roger Flores/HQ/3Com)
> >Subject: Re: beam failure
> >
> >
> >
> >
> >Well, after stepping through things in the PalmDebugger in assembly
> >language, it
> >looks like ExgAccept is doing something I didn't expect. I am setting the
> >Description and the Type fields in the socket structure when sending the data,
> >and leaving the Name NULL.
> >
> >On the receiving end, I am getting a Description, but the Type is NULL,
> >and the
> >name is Palm.exg. Since the source for ExgLibAccept is not available, it
> >is hard
> >to know how the exchange manager handles these parameters.
> >
> >When I do this in loopback mode, I get the Type as expected. I was relying on
> >the Type field to direct how to receive the beam.
> >
> >For David or Roger, what is the expected behavior for how the Type and Name
> >fields are filled in by ExgAccept? Also, how do you send something to another
> >app on the Palm using the Type field. For example, if you want to send
> >something
> >to another Palm's Memo Pad, but instead of specifying the Creator as the
> >MemoPad
> >creator, you instead want to specify the Type as "TXT"?
> >
> >Thanks,
> >
> >Shannon
>
>
>
>
>--
>For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palm.com/devzone/mailinglists.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hands High Software
Award winning software for the Palm(tm) Computing platform
<http://www.handshigh.com/>
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
