Fix wrong callback called bug 49/57949/4 accepted/tizen/ivi/20160218.023223 accepted/tizen/mobile/20160127.072634 accepted/tizen/tv/20160127.072800 accepted/tizen/wearable/20160127.072836 submit/tizen/20160127.015957 submit/tizen_ivi/20160217.000000 submit/tizen_ivi/20160217.000002
authorHyunho Kang <hhstark.kang@samsung.com>
Tue, 26 Jan 2016 08:42:23 +0000 (17:42 +0900)
committerHyunho Kang <hhstark.kang@samsung.com>
Wed, 27 Jan 2016 01:52:29 +0000 (10:52 +0900)
commit9a5b20926504bce3dde43d936d3b22ba68172a74
tree852f1bef76227fe1e8ef22c7ebbdbcb0c32c1bc4
parentd669543231d67b7ebb5e5ff6411f9875757655c5
Fix wrong callback called bug

When trusted and none trusted port registered with same
port name, message-port api can not tell which callback
should be called when socket transfer happened.
(after first communication)

Change-Id: Id599946aa0ffe7907225f9123c55fdbd0451fc12
Signed-off-by: Hyunho Kang <hhstark.kang@samsung.com>
src/message-port.c