You have just entered room "Chat 6406362670643895520."
x V DoGG x: ok
x V DoGG x: we are good
Eceguru: saw its due next week
x V DoGG x: what is that?
Eceguru: the book report
Eceguru: i thought it was after thanksgiving
Eceguru: but its next tuesday
x V DoGG x: yeah, i saw that a few weeks ago
x V DoGG x: did they chagne the date
x V DoGG x: cuz i had thought the same
starkiller76 has entered the room.
starkiller76: sorry I am late
Eceguru: ok
Eceguru: when did you think it was?
Abhi327 has entered the room.
Abhi327: hello everyone
sudigh has entered the room.
Eceguru: hi
sudigh: Hello
x V DoGG x: hey
Abhi327: vivek i sent you and kabe an email. i'll have the feedback for the api's by tomorrow morning. it looks good.
x V DoGG x: ok
x V DoGG x: i will check the other accnt
Eceguru: reminder that book reports are due next tuesday
x V DoGG x: ok
x V DoGG x: any plans for an agenda
sudigh: Lets wrap up the meeting fast. I have lots to read for the book report :-(
Abhi327: i put up an agenda
x V DoGG x: i did look around at some of the other project sites
Eceguru: how are we doing compared to them>
x V DoGG x: and they seem to be in similar stages as us, so we aren't behind... there is only one group that seems ahead of us
x V DoGG x: i noticed we have a plan for iteration 3... did we have one for 1 and 2?
Abhi327: ok. well today we need to go back with a clear idea of what we are delivering for the semester and who'll be working on what.
starkiller76: I will create an iteration plan for one and two
starkiller76: it is not pressing at the moment
sudigh: yes, lets finalise the modules for each of us.
Eceguru: sorry i didn't get the test plan finished yet. i had to work this weekend
Eceguru: should get it done either tonight or tomorrow night
x V DoGG x: ok, i was just wondering if we have something like this
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/106%3A+Metro+CertiTrack
x V DoGG x: showing the breakdown of our plans by iteration
x V DoGG x: if not, perhaps one of us should take it on
Eceguru: these guys look good
x V DoGG x: sorry, like this:
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Metro+CertiTrack+%3A+Project+Plan
x V DoGG x: yeah, they are the only ones that have such an elaborate plan
x V DoGG x: and website
starkiller76: they are mixing construction and elaboration
starkiller76: i don't agree with that
starkiller76 has left the room.
x V DoGG x: not sure where you see that on the second page
x V DoGG x: anyways
x V DoGG x: where should we begin
x V DoGG x: abhi, kabe, and i discussed the services and gui api
Abhi327: pull up the agenda.
starkiller76 has entered the room.
x V DoGG x: on friday, and it more or less cleared up a lot of confusion that we had and i think gave everyone a clearer picture on the tasks
x V DoGG x: ok
x V DoGG x: lets get starte
x V DoGG x: d
x V DoGG x: #1
sudigh: Will you elaborate on that a a bit, Vivek ?
x V DoGG x: sure.... it is kinda hard to capture the whole conversation (it was on the phone) but essentially
Abhi327: we decided to ido our design by deciding on the essential api's for the three layers.
x V DoGG x: it helped us understand the overall architecture of the application
Abhi327: this will essentially provide us with the necessary abstraction so that everyone can work on their own piece on a single layer without
Abhi327: worrying about HOW the other layers work
Eceguru: ok
sudigh: hmm
x V DoGG x: we decdided that it would be easiest to let the GUI and the Services layer communicate through java classes and shared memory space between threads, so that we don't have to spin off multiple processes that independantly
x V DoGG x: have to communicate over sockets or something like that.... it won't be necessary since we can spawn threads within an application to do the tasks that may hold up the main thread
x V DoGG x: the APIs that we started to define are available at:
sudigh: won't shared memory be a bottleneck for i/o purposes ?
x V DoGG x: http://www.thakkarweb.com/~vivek/cs327/linuxwifi/api/
Abhi327: i also had a chat with dave on saturday to discuss api's b/w the services and the core layer.
x V DoGG x: what do you mean a bottleneck
x V DoGG x: there is not much data moving between the layers
x V DoGG x: other than control information
Abhi327: sudipta can you clarify it further ?
sudigh: not all peers can access/modify data fast enough.
sudigh: whould also call for locks.
kabev1: peers don't use shared memory
kabev1: jsut the different layers
sudigh: locks in the data structures that the various layers are sharing
Abhi327: passing back data could be a lot of overhead. i don't see how shared memory could increase overhead. if you are using IPC's for process communication, we will end up using plenty of read/writes
Abhi327: hence any form of IPC is more overhead than shared memory
x V DoGG x: we shouldn't dwell on this point for long.... i think the discussion can go on forever
Eceguru: yes
x V DoGG x: we should stick to the agenda, but i just wanted to mention what we talked about
Eceguru: we can discuss that in our reviews
Eceguru: which we need to schedule
x V DoGG x: agree
Abhi327: anyways we'll have to review the design docuement. lets keep these discussions for later
x V DoGG x: yes
x V DoGG x: #1
x V DoGG x: implementation for this semester
x V DoGG x: i beleve someone had proposed implementing a bunch of the usecases by 11/27.... i am not sure that is actually possible
x V DoGG x: i think we should focus on "manual drive" mode aspect of the use cases with being able to search by one of the 5 attributes
Abhi327: ok lets talk about only in terms of deliverables(MUST) no wishlists
x V DoGG x: for this semseter
x V DoGG x: we can implement the rest next semester
Eceguru: i agree
Eceguru: we also have to remember that we need the RUP deliverables as well as working code
x V DoGG x: i think we should accomodate the core components of "download", "upload", "peer discovery" from one peer
Eceguru: so we need to have reviews and stuff like that
Abhi327: ok 1) auto-detect 2) manual search/download/upload correct ?
Eceguru: those should be fine
Eceguru: and lets make sure we follow the process strictly for those peices
Eceguru: i think the process part will be a huge part of the grade
Eceguru: more so than code that has all the features
kabev1: I agree w/Isaac
x V DoGG x: yes...
Abhi327: we'll be judged on our process not on our deliverables. i completely agree
kabev1: on that point what deliverables do we have?
kabev1: so far
Eceguru: an iteration plan
x V DoGG x: Ok... let me arbitrate
starkiller76: product is half our grade
x V DoGG x: please add to the list
Abhi327: 1) Project plan 2) Design doc 3) CM 4) Requirements 5)Testing
x V DoGG x: or abhi....
Abhi327: sorry i was busy typing wasn't looking at the screen:-)
x V DoGG x: no prob
x V DoGG x: its ok, go ahead
x V DoGG x: are we defining deliverables or process artifacts?
x V DoGG x: or code?
Abhi327: 6) code
Abhi327: anythign else ?
Eceguru: think that's all
x V DoGG x: correct
starkiller76: has anybody read the RUP book
x V DoGG x: nope
Eceguru: no
starkiller76: i have
kabev1: a little
sudigh: Yes
starkiller76: it has us breaking things up based on use cases
starkiller76: I spent alot of time on our iteration plan
starkiller76: basically i have to rewrite the whole thing
Eceguru: i think the plan is fine
Eceguru: maybe move the dates around
starkiller76: but we are not implementing use cases anymore
Eceguru: i think we have to implement use cases still
Eceguru: the question i think is which ones need to be done
starkiller76: ok
x V DoGG x: i don't know that our usecases can be broken up
x V DoGG x: so that we only implement a few of them
starkiller76: i see
Eceguru: i think they can
x V DoGG x: ok, what do you propose?
Eceguru: we don't need to do resume download for instance
starkiller76: i just need to update deadlines etc.
Eceguru: i don't have the plan with me
Eceguru: but i think it only said when the first 4 use cases would be done
Eceguru: or am i wrong
x V DoGG x: ahhh i see
starkiller76: i changed that
starkiller76: I need to repost it on the website
x V DoGG x: lets do 1, 2, 3, 5....
Eceguru: yes
x V DoGG x: does everyone agree?
starkiller76: Ok i will update the plan
Eceguru: i think that's what we talked about last week
x V DoGG x: ok
starkiller76: yeah
x V DoGG x: sorry, short term memory
Abhi327: sure
Eceguru: and what we wanted to get done first
x V DoGG x: very short :-)
starkiller76: sorry, I just wanted to be clear:-)
Eceguru: the other cases aren't realistic
x V DoGG x: yes
x V DoGG x: i agree
Eceguru: in the timeframe
starkiller76: I agree to
Abhi327: yeah lets plan on just these four
x V DoGG x: so we have defined #1
x V DoGG x: we can move on, correct?
starkiller76: yep
Abhi327: yes
x V DoGG x: i will outline the artifacts and deliverables as discussed in the summary of this meeting
x V DoGG x: for review next week
x V DoGG x: #2
x V DoGG x: Abhi made a good point at our discussion on friday
x V DoGG x: I agree that we should split up implementation by who designed the aspects
x V DoGG x: as it would be easiest for those who designed the GUI and its' API to code it....
x V DoGG x: since they would understand how they were envisioning it during design
x V DoGG x: does that make sense?
starkiller76: sure
x V DoGG x: thus we don't waste a lot of time relearning
x V DoGG x: knowledge that we already have in various parts of the grou
x V DoGG x: p
x V DoGG x: Perhaps some layers have more work than others
x V DoGG x: do any pairs feel they have more work than they can handle
Abhi327: yes the API's b/w the services and UI are already being developed.
x V DoGG x: in their layer?
Abhi327: I am working on identifying everything that needs to be passed b/w the services and core. I'll work with dave on it.he is our in-house expert on jxta:-)
starkiller76: thanks, I am blushing
Abhi327: we can now focus on just the four usecases
Eceguru: sorry, have an emergency at work right now
Eceguru: a rat or possum is lose
Abhi327: i plan to distribute the api set and details class diagrakms before this weekend so everyone knows how to use them and what to implement
Eceguru: back in a sec
starkiller76: ok
x V DoGG x: he he :-)
x V DoGG x: issac, where is it?
x V DoGG x: i gotta see this....
x V DoGG x: more fun at motorola
x V DoGG x: anyways
x V DoGG x: anything else for #2
x V DoGG x: ?
Abhi327: issac, bad security :-)
x V DoGG x: i assume at this point we can just start coding as the APIs are finalized
x V DoGG x: we should set a milestone
x V DoGG x: for design specs
Abhi327: I put that for Thursday NOON
x V DoGG x: and some set of code
x V DoGG x: ok
Abhi327: We also need to 1) distribute modules for services layer(#2) 2) someone to work on what to intergarate as part of core layer 3) any expertise in xml parsing/generation ?
starkiller76: i am working on the xml
sudigh: I can work on 2
starkiller76: java has some built in parsers
Abhi327: yes
Abhi327: i sent you the links for it today:-)
x V DoGG x: cool....
starkiller76: but I am not an xml expert, so I could use help
x V DoGG x: so we can move on to number #2 part 2
Abhi327: ok sudipta, you wanna work on integrating the core layer to the rest of the app. it might be a lot of work. ??
starkiller76: Issac and I can help
sudigh: sure, I can do that. Anyone lese interested to do that me ?
sudigh: lese = else
Abhi327: we'll need major help in the services layer. most of the coding lies there
starkiller76: I have tested the JXTA core
sudigh: I can help out in the services layer if required.
starkiller76: so Sudipta, Isaac, and Dave
x V DoGG x: ok
sudigh: have we decided upon the format for our config file ? I know it is a plain text file, but still a rough format.
x V DoGG x: abhi, kabe, and i discussed a pipe delimited text file
x V DoGG x: on friday wihtout details
starkiller76: can we parse that into XML
Abhi327: ok sudipta and dave work on the core layer. issac was working on some search or download stuff(services layer)
x V DoGG x: if everyone wants to, xml can be used.....
sudigh: maybe we can get some open source xml parser.
x V DoGG x: you can't parse a pipe delimited file into xml.... but we can just use XML to define the file
starkiller76: JXTA uses XTA to broadcast advertisements
x V DoGG x: yes.... i know of one
sudigh: I'll lookout for that.
starkiller76: XTA=XML
x V DoGG x: one = xml parser
starkiller76: If we keep everything we can in xml it will make it easier to work with the JXTA protos
sudigh: I agree wth Dave.
Abhi327: Sudipta and Dave (core layer intergration includes XML encode/decode)
sudigh: cool.
Abhi327: does that sound ok ?
starkiller76: yes
sudigh: sound good.
Abhi327: ok
Abhi327: we need to distribute the other modules
Abhi327: and there are plenty in the services:-)
sudigh: I also try to come up with milestones for the various tasks, this'll be an ongoing thing.
x V DoGG x: kxml.org
x V DoGG x: is the open source parser that a friend of mine usees
Abhi327: and we have Issac, Kevin, Guru, and Abhi
Abhi327: we can take that offline. i'll send out an email and we can distribute the work in the services and let the group know since we are missing kevin and guru at the moment
x V DoGG x: ok
Abhi327: off to 2nd 2)
x V DoGG x: Kabe?
kabev1: Present
sudigh: I found a very good tool for class diags on the web, free called Visual Paradigm.
x V DoGG x: i am about to fireoff the doc you just sent me
kabev1: All you ol' buddy
sudigh: I'll update my class diags with that tool and uploda them on the wiki page.
sudigh: But this will again be an ongoing thing, as I'll add more with time.
kabev1: Vivek is sending my first version of the CM plan. It is not complete, and I need to figure out some stuff with SOurceforge
x V DoGG x: its off
x V DoGG x: i am volunteering to be on the CCB
x V DoGG x: ok
x V DoGG x: did everyone get it
kabev1: Here's something we need to address
kabev1: We need a change control board....
kabev1: Basically we should look take all existing artifacts and treat any modification as a change
kabev1: err change request... and this should be proiritized and assigned by the CCB
kabev1: This will allow for metrics
x V DoGG x: i will volunteeer
kabev1: kinda like the reports in Office Space ;-)
x V DoGG x: plus this way we aren't all working on random little enhancements
Abhi327: guys i'll be away for the next few minutes. i'll check the logs if i miss the meeting. i am still at work.
x V DoGG x: ok
x V DoGG x: well.. since the discussion is dead
x V DoGG x: lets move on
x V DoGG x: #3
x V DoGG x: Requirements
x V DoGG x: how are they coming along
kabev1: People on the board need to meet and go over all requesta
kabev1: I should have it set up by this weekend
x V DoGG x: helooooo?
kabev1: Not the requirements... Anyone still out there?
x V DoGG x: kevin?
x V DoGG x: should we call it a meeting?
Abhi327: has anyone got hold of kevin. i haven't been able to get ni touch with him for more than a week
x V DoGG x: not heard from him
x V DoGG x: i can email him right now... lets see if he responds
sudigh: not me
kabev1: OK, I propose we wrap up the meeting, it's already been a long meeting
kabev1: Move the rest to wed.
kabev1: rejections?
x V DoGG x: sounds good
x V DoGG x: i don't hear anything
x V DoGG x: not that i would
x V DoGG x: since this is text chat
x V DoGG x: i will post the logs
x V DoGG x: good bye!