1 rizwank 1.1 %META:TOPICINFO{author="ThomasKho" date="1107736890" format="1.0" version="1.4"}%
 2             %META:TOPICPARENT{name="Group4"}%
 3             ---++ February 4, 2005 Deadline
 4             Our stated deliverables for this 2005-02-04 deadline are as follows:
 5             
 6             	* Start design for conformance testing of DLL%BR%
 7             	Dan Kegel suggested several ways to build a conformance test for wsock32. Our main goal for this test is to create a multi-threaded network client and server that use blocking I/O to communicate. This test will strive to model a typical application that uses wsock32.
 8             		* Outline common uses of DLL functions%BR%
 9             		wsock32.dll is a common socket library for Windows (it implements 32-bit Windows Sockets 1.1). It's used by virtually every network-aware application. The most critical functions are:
10             			* WSAStartup()
11             			* socket()
12             			* WSACleanup()
13             			* WSAGetLastError()
14             			* bind()
15             			* listen()
16             			* accept()
17             			* connect()
18             			* send()
19             			* recv()
20             	* Build basic conformance test with ~3 function
21             		* Setup CVS, changelog, news%BR%
22 rizwank 1.1 			* We are using the CVS setup by Wine 3 member Rizwan at http://www.geekymedia.com/cvs
23             			* Our ChangeLog and News files have been created, and are stored in CVS, accessible from our main wiki page at [[Group4]]
24             		* Build sample Win32 app
25             			* [[%ATTACHURL%/2005-02-06WinTestOK.tiff][2005-02-06WinTestOK.tiff]]
26             			* [[%ATTACHURL%/2005-02-06Win32BuildOK.tiff][2005-02-06Win32BuildOK.tiff]]
27             		* Add function test cases
28             			* Simple use of threading for client/server code. Need synchronization of threads at end.
29             			* Use of initialization function WSAStartup()
30             		* Test functionality in Linux%BR%
31             		Building the test in linux was a huge hurdle in itself. There are some notes on creating a functionaly test in [[Group4Progress]]
32             			* [[%ATTACHURL%/2005-02-06LinuxBuildOK.tiff][2005-02-06LinuxBuildOK.tiff]]
33             			* [[%ATTACHURL%/2005-02-06LinuxTestOK.tiff][2005-02-06LinuxTestOK.tiff]]
34             		* Get feedback from CS 130 Wine groups
35             			* We have been actively talking with Group 3 (Rizwan) about progress and hurdles via instant messenger.
36             
37             -- Main.ThomasKho - 04 Feb 2005
38             
39             %META:FILEATTACHMENT{name="2005-02-06WinTestOK.tiff" attr="" comment="" date="1107736530" path="2005-02-06 Win Test OK.tiff" size="92500" user="ThomasKho" version="1.1"}%
40             %META:FILEATTACHMENT{name="2005-02-06Win32BuildOK.tiff" attr="" comment="" date="1107736576" path="2005-02-06 Win32 Build OK.tiff" size="87874" user="ThomasKho" version="1.1"}%
41             %META:FILEATTACHMENT{name="2005-02-06LinuxBuildOK.tiff" attr="" comment="" date="1107737004" path="2005-02-06 Linux Build OK.tiff" size="65000" user="ThomasKho" version="1.1"}%
42             %META:FILEATTACHMENT{name="2005-02-06LinuxTestOK.tiff" attr="" comment="" date="1107737024" path="2005-02-06 Linux Test OK.tiff" size="50736" user="ThomasKho" version="1.1"}%
43 rizwank 1.1 %META:TOPICMOVED{by="ThomasKho" date="1107502124" from="WineDev.20050204Submission" to="WineDev.2005-02-04Submission"}%