6.4 Limitation of Infomediary Device Pass by Movement Speed

6.4  Limitation of Infomediary Device Pass by Movement Speed

6.4.1        Test Design

The time required for database synchronization process between infomediary device and server computer calculated to find the recommended movement speed of the infomediary device for ensuring the database synchronization is complete. It is to find an ideal period of time infomediary device should remain in Wi-Fi access point range of server computer. The range of the network connection between infomediary device and Wi-Fi access point of server computer measured. The transfer rate of Wi-Fi access point is compared with the offline email system storage read and write speed limitation. Based on this transfer rate, size of data and network range, the speed movement of the infomediary device passes by server computer network connection can be calculated. This test is to ensure the database synchronization process is performed completely successfully. 

Citra : 3DS emulator boot first commercial game Zelda Ocarina of Time 3D

Citra finally boot it's first commercial game Ocarina of Time 3D. The game manage to go ingame with average speed 3 FPS.

This is still premature beginning of the next major work by Citra team.

Against similar 3DS emulator such as 3dmoo and TronDS, Citra already beat them at this moment.

Citra is an experimental open-source Nintendo 3DS emulator/debugger written in C++. It is written with portability in mind, with builds actively maintained for Windows, Linux and OS X. Citra only emulates a subset of 3DS hardware, and therefore is generally only useful for running/debugging homebrew applications. At this time, Citra is even able to boot several commercial games! None of these run to a playable state, but we are working every day to advance the project forward.

Citra is licensed under the GPLv2. Refer to the license.txt file included. Please read the FAQ before getting started with the project.

Unfortunately there in no dedicated forum for this emulator. They should after all to speed up the development.

Video showing Ocarina of Time 3D running on Citra. Be warn that this is not the actual speed run on emulator.

6.3.3 Test Result

6.3.3 Test Result

         This offline email system queue delay period was set to30 minutes with maximum retries value 2147483647. The status of the queue message available in the mail server administrator control pages. The email from user offlineA was sent to user onlineC and found that pending email data was remaining on the Mail Server after a period of testing time as shown in the Table 6.2. Test result is produced by actual conduct test.

Delay Period Test Result

Table 6.2: Delay Period Test Result

6.3.2 Expected Outcome

6.3.2 Expected Outcome

         This offline email system expected to be able to tolerate with a long period of delay communication between offline network environment and online network environment. The email data expected to be remain in the mail server and keep in pending status for 60 minutes ( one hour), 1440 minutes (one day) or 10080 minutes (one week) and successfully reach the destination after process of database synchronization completed.

6.3 Delay Test

6.3     Delay Test

6.3.1        Test Design

           Minutes between every retry setting defines how many minutes mail servers should wait before every retry delivering emails to other servers. The default value is 60 minutes. As explained in chapter 4.2, this offline email system queue delay period was set by the email system administrator where the email data can be kept in temporary storage for a maximum period of 2147483647 minutes equal to 1491308 days. This offline email system delay time was set to 30 minutes. The email data will remain and not discarded for 30 minutes until a next retry. When every email was sent successfully from the sender to the receiver in the delay period range of time, its mean the mail data are remaining stored in mail server and synchronization is successfully performed.

           Number of retries setting defines the number of times mail server should try to deliver an email when the deliveries failed. Email failed to deliver when the receiving mail server such as Gmail cannot be reached or the network is not available. The default value of number of retries setting is 4 retries. This means hMailServer will try a total of 5 times before giving up and returning an error message to the sender. The maximum value is 2147483647 retries. This offline email system number of retries was set to maximum 2147483647. This means that the email data is kept in the database for 30 minutes until next retries and repeated until maximum 2147483647 retries. The email data will only discard when the maximum retries value which is 2147483647 is exceeded. Delay period test performed for sending email with delay 60 minutes, 1440 minutes and 10080 minutes.

6.2.3 Test Result

6.2.3        Test Result

            The email system functionality result for each test 1, test 2, test3, test4, test 5 and test 6 shown in Table 6.1. Test result is produced by actual conduct test. Test 1 is testing send and receives of email between user offlineA and user offlineB, test 2 is testing send and receives of email between user onlineC and user onlineD, test 3 is testing send and receives of email between user onlineC and Gmail through internet, test 4 is testing send and receives of email between user offlineA and user onlineC, test5 is testing send and receives of email between user offlineA and Gmail and test 6 is testing send and receives of email between user onlineC and Gmail from local mail server to the internet. All email communication tests contain sample attachment files.

Send and receive email test result on each node

Table 6.1: Send and receive email test result on each node

6.2.2 Expected Outcome

6.2.2        Expected Outcome

Expected outcome from all five test samples as shown in Figure 6.3 as per below:

Test 1: Connectivity test between offline users at offline mail server in Test 1 should show that user offlineA and user offlineB can successfully send and receive email.

Test 2: Connectivity test between online users at online mail server in Test 2 should show that user onlineC and user onlineD can successfully send and receive email.

Test 3: Connectivity test between online user at online mail server and internet user in Test 3 should show that user onlineC and gmail user can successfully send and receive email. This is the same result for Test 6.

Test 4: Connectivity test between offline user at offline mail server and online user at online mail server in Test 4 should show that user offlineA and user onlineC can successfully send and receive email with the help of infomediary device.

Test 5: Connectivity test between offline user at offline mail server and internet user in Test 5 should show that user offlineA and gmail user can successfully send and receive email with the help of infomediary device.

6.2 Connectivity Test

6.2  Connectivity Test

6.2.1        Test Design

            There are six test samples as in Figure 6.3. Test 1 involves sending and receiving emails between user offlineA and user offlineB through offline environment LAN. Test 2 involves sending and receiving emails between user onlineC and onlineD through an online environment LAN. Test 3 involves sending and receiving emails between user onlineC and an internet email such as Gmail through the internet. Test 4 involves sending and receiving emails between user offlineA and user onlineC through infomediary device with DTN based technique. Test 5 involves sending and receiving emails between user offlineA and Gmail through an infomediary device with a DTN based technique where the mail data is being transitioned on the online mail server before it being sent to the Gmail. Test 6 involves sending and receiving emails between user onlineC and Gmail from the online environment LAN directly to the internet.

Connectivity Test

Figure 6.3: Test sample

6.1.3 Test result

6.1.3        Test result

            The registration page is only accessible from LAN which connected to online mail server or through internet. Characters such as "? * |  \ / < >" does not supported in creating an email account. Figure 6.2 shows new account registration test result through internet at webmail address which is http://pemail.suroot.com by following the register button, filling in the anti spam security code and setup the username and password for the new email. The same procedure also performed on the local online mail server at the local webmail address which is http://192.168.1.7/pemail.

New account registration test result

Figure 6.2: New account registration test result

            Database synchronization application on the online server computer is synchronizing the mail database into infomediary device and transferring it to the offline server computer. All the new email accounts which are created in this test such as offlineA@pemail.suroot.com, offlineB@pemail.suroot.com, onlineC@pemail.suroot.com and onlineD@pemail.suroot.com was tested on the offline environment network. All emails are successfully login, working and listed in the mail server administrator pages. Test result is produced by actual conduct test.