Implement bare-bones AS_SYNC message handling - this fixes a problem whereby app_server<->client communications would come to a stop since the client expected a reply from this message and would never get one because it was unimplemented
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9711 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
parent
ec2680f053
commit
f260cedb5a
@ -2182,6 +2182,13 @@ debugger("STROKERECT");
|
|||||||
|
|
||||||
break;
|
break;
|
||||||
}
|
}
|
||||||
|
case AS_SYNC:
|
||||||
|
{
|
||||||
|
// TODO: AS_SYNC is a no-op for now, just to get things working
|
||||||
|
fMsgSender->StartMessage(SERVER_TRUE);
|
||||||
|
fMsgSender->Flush();
|
||||||
|
break;
|
||||||
|
}
|
||||||
default:
|
default:
|
||||||
{
|
{
|
||||||
printf("ServerWindow %s received unexpected code - message offset %lx\n",fTitle.String(), code - SERVER_TRUE);
|
printf("ServerWindow %s received unexpected code - message offset %lx\n",fTitle.String(), code - SERVER_TRUE);
|
||||||
|
Loading…
Reference in New Issue
Block a user