not really. serial is just a hardware medium for transferring data bytes.
IF the databytes were Appletalk packets, depending on the MTU setting of the adapter, those appletalk packets would be encapsulated into TCP/IP packets at the module then transmitted to the socket connection. If the module encapsulates the Appletalk packets the same way as the mac would, then it should work. (not sure how mac does its encapsulation, but the wifly manual states how its own encapsulation works).
If you encapsulate serial localtalk packets as they are, which is what i mentioned in my last post, then yes appletalk IP devices may not recognize them. But if you customized a driver to send appletalk IP packets over serial connected wifly instead of localtalk, itll probably work just fine.
Or, you could just put another wifly module at the other end and itll take the localtalk over TCP/IP back to standard localtalk serial again. Kinda the same thing.
IF the databytes were Appletalk packets, depending on the MTU setting of the adapter, those appletalk packets would be encapsulated into TCP/IP packets at the module then transmitted to the socket connection. If the module encapsulates the Appletalk packets the same way as the mac would, then it should work. (not sure how mac does its encapsulation, but the wifly manual states how its own encapsulation works).
If you encapsulate serial localtalk packets as they are, which is what i mentioned in my last post, then yes appletalk IP devices may not recognize them. But if you customized a driver to send appletalk IP packets over serial connected wifly instead of localtalk, itll probably work just fine.
Or, you could just put another wifly module at the other end and itll take the localtalk over TCP/IP back to standard localtalk serial again. Kinda the same thing.