[Registry-dev] Chat Log - Hackathon day1

Tue Oct 30 04:59:56 PDT 2007

On the topic of DB vs. FS backend- I agree we can have different backends. 
However, for a start I'd prefer to have a pure DB backend and have 
checkin/checkout command line tools in addition to the API. That's a 
fairly simple client on top of the API.

Sanjiva.

Deepal Jayasinghe wrote:
> Hi all,
> 
> I do not think we are going to have anymore discussion in the IRC and we
> are doing coding , so here is the chat log so far.
> 
> 
> * Deepal changes topic to 'WSO2 Registry Hackathon'
> * sanjiva has joined #wso2-registry
> <sanjiva> hi ..
> <sanjiva> going to sleep but I'll leave this on :). have fun!
> <sanjiva> Please log the chat and post it to the list later.
> <Deepal> will do
> <Deepal> Jonathan just came
> * Marsh has joined #wso2-registry
> * sanjiva_ has joined #wso2-registry
> * sanjiva has quit IRC (Read error: 113 (No route to host))
> * gdaniels has joined #wso2-registry
> <gdaniels> hi all!
> <Deepal> hi Glen
> <Deepal> small discussion on what we are going to do
> <gdaniels> conquer the world, right? :)
> <Deepal> do we want to store the real data in DB or filesytem
> <Deepal> if we do store in the DB , we can call chcekout and chcek in
> <Deepal> as we can find in jackrabit (which is very cool API AFIK)
> <gdaniels> there are (at least :)) two major questions here
> <gdaniels> 1) what does the CLIENT API look like
> <gdaniels> that's independent of the backend technology
> <Deepal> think abt the case where we have js page
> <gdaniels> 2) what does our server do in its implementation, and what
> kinds of back ends can it deal with
> <Deepal> in the file system
> <Deepal> and if we store in the DB , how can we edit , but if the file
> is in the filesystem we can easily edit that
> <gdaniels> file system back end should absolutely be possible
> <gdaniels> and maybe even import/export to FS, regardless of actual
> runtime storage mechanism
> <Deepal> that is chcekout and chcek in :)
> <gdaniels> perhaps
> <gdaniels> remember there's a use case here where we want to be able to
> just use the registry API to access and modify a synapse.xml/axis2.xml/etc
> <gdaniels> so I think it's likely we want to be able to support
> different backends plugged in at different places in the hierarchy...
> <gdaniels> (maybe - haven't thought that all the way through yet)
> <Deepal> yes
> <Deepal> yes
> <gdaniels> one thing we talked about but haven't yet followed through on
> is building a better list of scenarios and storing them somewhere...
> <gdaniels> I'm still of the opinion that, although it takes some time
> and effort to do that, it's worth it so you make sure you don't lose
> sight of anything as you build
> <Deepal> I agree , mashups is good scenario
> <Deepal> to start with
> <Deepal> b'coz they are going to use registry havily
> <gdaniels> sure.  Synapse/ESB and Axis/WSAS also.
> <Deepal> so what they looking from registry , will be the starting point
> of register use case scenario
> <Deepal> yes sound good
> <Deepal> we are going to discuss what we need to do in mashups , a list
> of items
> <Deepal> we need to do
> <gdaniels> +1
> <Deepal> need to have a user page
> <Deepal> advanced serach page
> <gdaniels> (if you can put them in the wiki or type them in here that
> would be great)
> <Deepal> will do
> <Deepal> a set of permissions
> <Deepal> Ajax rating
> <gdaniels> "Ajax rating"?
> <Deepal> yes (to rate the mashups)
> <gdaniels> the AJAX part is incidental though, right?
> <Deepal> user favorits
> <Deepal> let's discuss one by one in datils soon :)
> <gdaniels> k
> <Deepal> at the moment we are listing out what we need to have
> <Deepal> User profile
> <Deepal> RSS and Atom feed
> <gdaniels> RSS and Atom feed of what?
> <Deepal> uers mashups ....
> <Deepal> once user login need to shows up the quries that he has created
> and provide a way to delete them
> <Deepal> how do we intefrate live mashups ? ....
> <gdaniels> (note: find better word than "queries" for the user interface)
> <Deepal> +1
> <gdaniels> integrating live mashups... you mean how do we display live
> results from mashups?
> <Deepal> no , how to deploy them
> <Deepal> from development stage to live system
> <Deepal> smt like that
> <gdaniels> so "promote mashups from dev to production"?
> <Deepal> yes , smt like that :)
> <Deepal> btw I am just typing what others are discussing for reference
> <gdaniels> the earlier we get these things precise, the easier it will be
> <Deepal> let's discuss them soon
> <gdaniels> yes, I know :)
> <deepalj> seems like , User managment ppl broken the build
> <deepalj> they have changed the DB scripts
> <deepalj> w.o letting us know :(
> <gdaniels> :( indeed
> <sanjiva> deepal send a message to commons dev and tell them they can't
> do that!
> <sanjiva> db scripts are part of the API when people start writing queries
> <gdaniels> well...
> <sanjiva> actually, why did it break the build now; don't the scripts
> come from the project itself?
> <gdaniels> this is the problem when you've got pre-1.0 code depending on
> pre-1.0 code :)
> <sanjiva> :)
> <sanjiva> fair enough .. but an email doesn't cost anything
> <gdaniels> sure
> <gdaniels> coordination is paramount
> <sanjiva> except discipline .. that's what I'm pushing for
> <gdaniels> +100
> <sanjiva> changes are a necessary thing; absolutely
> <gdaniels> :)
> <deepalj> Chathura is trying to fix the issue
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +1 650 265 8311 | +94 77 787 6880

"Oxygenating the Web Service Platform."