<HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
<META content="text/html; charset=euc-kr" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: ±¼¸²Ã¼, arial; MARGIN-TOP: 5px
}
TD {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: ±¼¸²Ã¼, arial; MARGIN-TOP: 5px
}
LI {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: ±¼¸²Ã¼, arial; MARGIN-TOP: 5px
}
BODY {
FONT-SIZE: 9pt; FONT-FAMILY: ±¼¸²Ã¼, arial; MARGIN: 10px; LINE-HEIGHT: 1.4
}
</STYLE>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META name=GENERATOR content="MSHTML 11.00.9600.18098"></HEAD>
<BODY>
<P>>> Also (on the patch) it looks like if there is an error it destroys the<BR>>> wl_socket object, could this do the wrong thing if the fd was supplied from<BR>>> outside?<BR><BR>> So like if the socket object couldn't be initted or added to the display<BR>> for some reason, it will call wl_socket_destroy() on the socket, which<BR>> will close the file descriptor and the fd lock. So I guess this<BR>> question basically boils down to is it allowed for the client to close<BR>> the file descriptor it was given?<BR><BR>> I'll defer to Sangjin on that but I should imagine that the client is<BR>> being given a unique file descriptor to use as it sees fit, including<BR>> closing it. Even without errors, Wayland will eventually call<BR>> wl_socket_destroy at program exit, so the fd is destined to be closed<BR>> one way or another.</P>
<P>I also think like bryce.<BR><BR></P>
<TABLE id=confidentialsignimg>
<TBODY>
<TR>
<TD NAMO_LOCK>
<P><IMG border=0 src="cid:Z5JE7EUABGFC@namo.co.kr"></P></TD></TR></TBODY></TABLE></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d1c4c6a24968fb25d351487f04c56dcbabf594055c454f66d261643f4e17952232c2d5b092db2212f255f74e40bd48632fd4ff3ea410d012fea75954dce1604da728c55b39cc59eacf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'>