On 12 Apr 2012, at 17:46, Pushpalanka Jayawardhana wrote: > Hi Scott, > > Thought it will be better to keep this thread updated on the progress I > made.
Great! Thanks for the updates - it makes sense to keep the thread going. > > Meanwhile I looked into the widget code and possible implementation of > verifying function. I placed a sample signature file inside a .wgt and > tried to access it inside Wookie. Inside W3CWidgetFactory class of parser > could get into the signature file with > *unzippedWidgetDirectory.getCanonicalPath() + File.separator + > "signature.xml".* Identification can be done,considering the naming > conventions in the spec for authors and distributors, when more signatures > are present. > * > * > As next step, I hope to look at how the decision of verification function > can take effect in deploying the .wgt at Wookie and taken into > other higher levels. Working on this is becoming more interesting now. Yes, as W3CWidgetFactory is the front API for the parser lib - for both the Wookie server and other W3C implementations reusing it - so it needs to have easy to understand/well documented method signatures so poses more of a design challenge. > > -- > Pushpalanka Jayawardhana | Undergraduate | Computer Science and Engineering > University of Moratuwa > > +94779716248 | http://pushpalankajaya.blogspot.com > > Twitter: http://twitter.com/Pushpalanka | Slideshare: > http://www.slideshare.net/Pushpalanka
