Article Review 5 
Article Review:

Vijish Vijayan
http://sites.google.com/site/vijishsite ... s-articles
Replication in Ficus
Distributed File Systems
http://sites.google.com/site/vijishsite ... =0&d=1

Target Audience
The target audience would be academics who are interested in the topics of data replication. In addition people interested in the Ficus framework for UNIX systems would be a target audience member as well.

Type of Document
Informative document that describes a research and development process, as well as the product of that process in detail. This document was a paper that was presented at a workshop concerning the replication of data - in 1990, that was a long time ago.

Summary of Article
The article starts out by introducing Ficus - this framework that can be added to many existing systems to support data replication and access easily. Next it explains the research process, their design model and then their approach. Finally they explain in more detail, the final product - Ficus.

Conclusion
This is a very old paper, I would be surprised if Ficus is still around - actually their website hasn't been updated in 4 years and development stopped in 95. Therefore this is a good article to understand the basics of some of the structures in data replication management.


[ add comment ] ( 23 views )   |  permalink
Presentation  
My Volunteer presentation from 11/11/09 on Distributed Javascript -
http://www.korykirk.com/CSC8530/images/ ... cript.pptx

[ add comment ] ( 6 views )   |  permalink
Screenshots & Test Cases 
The following screenshot is the output of my basic test code. The beginning is the automatic directory loading, and then the last line is the string output of my HiddenService object (the one that represents the service host). More details can be read about what the different variables represent and how they are calculated can be found in the specs: https://git.torproject.org/checkout/tor/master/doc/spec/rend-spec.txt or my notes: http://korykirk.com/CSC8530/images/hidden%20service.txt

All this code can be found at my github http://github.com/koryk/JTor



The output is as follows:

[11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: moria1 128.31.0.34:9031 fingerprint=ffcb46db1339da84674c70d7cb586434c4370441 v3ident=e2a2af570166665d738736d0dd58169cc61d8a8b) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: moria2 128.31.0.34:9032 fingerprint=719be45de224b607c53707d0e2143e2d423e74cf) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: tor26 86.59.21.38:80 fingerprint=847b1f850344d7876491a54892f904934e4eb85d v3ident=14c131dfc5c6f93646be72fa1401c02a8df2e8b4) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: dizum 194.109.206.212:80 fingerprint=7ea6ead6fd83083c538f44038bbfa077587dd755 v3ident=e8a9c45ede6d711294fadf8e7951f4de6ca56b58) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: Tonga 82.94.251.206:80 fingerprint=4a0ccd2ddc7995083d73f5d667100c8a5831f16d) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: ides 216.224.124.114:9030 fingerprint=f397038adc51336135e7b80bd99ca3844360292b v3ident=27b6b5996c426270a5c95488aa5bceb6bcc86956) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: gabelmoo 80.190.246.100:80 fingerprint=68333d0761bcf397a587a0c0b963e4a9e99ec4d3 v3ident=81349fc1f2dba2c2c11b45cb9706637d480ab913) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: dannenberg 213.73.91.31:80 fingerprint=7be683e65d48141321c5ed92f075c55364ac7123 v3ident=585769c78764d58426b8b52b6651a5a71137189a) [11/11/09 4:40 PM] DEBUG: Adding trusted authority: (Directory: urras 208.83.223.34:443 fingerprint=0ad3fa884d18f89eea2d89c019379e0e7fd94417 v3ident=80550987e1d626e3eba5e5e75a458de0626d088c)



Hidden Service: JTor Test hidden service:6112-6120 Permanent ID : 1C04EEF2CFCFEA948C3C Service Descriptor : 2631362A025C773CD5B00F8343E5427CE07F711B Tor Public Key: bd56e37e79e7311bb665e2861f4d744866794c6a


This is just the server side of the Hidden Services, and I still need to implement the Rendezvous point circuits. And then I will have to finish the client side as well. After that, sufficient testing would be providing a service with the jTor hidden services, and then trying to connect to it not using the jTor client and vice versa. That would ensure workability as well as compatibility with the other versions of the client.


[ add comment ] ( 6 views )   |  permalink
Article Review 4 

Article Review:
http://www.mil-embedded.com/pdfs/Rydal.July07.pdf
Multi-Level security in tightly coupled military systems:
Virtualization as a path to MLS
From: Matt Anders http://thetravelingdeveloper.com/

Target Audience
The military, or people interested in high security for large
systems. It is informative so it could be for any person who
stumbles upon it - but I don't think someone would be interested
in this unless he/she likes security and/or is part of the
military.

Type of Document
This is an informative document created by academic
professionals. It is brief, but to the point about their
comparisons of virtualization and MLS.

Summary of Article
compares and contrasts virtualization to MLS. They do this by
comparing and contrasting certain elements about the two, their
goal and how they isolate data. The isolation of data is
certainly stressed in this article, because it is their measure
of security. Their solution to what each of these don't have is
the RapidIO network protocol. In their conclusion they claim
that RapidIO could bring security to traditional and virtualized
networks.

Conclusion
This is a good informative document about Virtualization and
Multi-Level Security - their differences and similarities, goals
and how they work; however it is mostly a plug for the RapidIO
network protocol.



[ add comment ] ( 22 views )   |  permalink
Article Review 3 
Daniel Priece: http://www05.homepage.villanova.edu/dan ... e/csc8530/
Article: http://www.ddj.com/219501439


Target Audience
This is targeted at professionals more than it is academics. The application of the technology that surrounds this article mostly seems applicable in a infrastructure business setting.

Type of Document
This document is a Journal article. It explores multiple ways on paralellizing legacy code and the pros and cons of each way. It is somewhat an instructional article and also an educational article.

Summary of Article
Companies with legacy code would like to find a way to easily parallelize that code, but it is not such an easy task. In many cases, the most robust way is to rewrite an architecture to interface over the legacy code and make it thread safe from the bottom up. But this of course requires a reconstruction of the system. Another approach is to distribute the most computationally intensive parts of the legacy code. The article goes into some suggested hardware specs for distributing. This article then summarizes the Fine Grained Distributed Processing approach for parallelizing legacy code.

Conclusion
The Fine Grained Distributed Processing approach is a good approach if you want an easy way to parallelize legacy code. However, there are certain constraints to which this approach works. These constraints are the message length and how easy it is to create a message. But if there is relatively simple message passing in legacy code then The Fine Grained Distributed Processing approach would be a good choice for doing so.

[ add comment ] ( 22 views )   |  permalink

<Back | 1 | 2 | 3 | Next> Last>>