Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

What exactly does "all the public methods" mean?

 
Skip Cole
Ranch Hand
Posts: 177
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
When the specs say:
"The remote client code that you write must provide all the public methods of the suncertify.db.Data class."
How are you interpreting this?
This seems to say that we need to be able to do every possible operation to the database from the client, even though the rest of the specs seem to imply we simply need to be able to query and book.
I am doing this using serialized objects (now I see the error of my ways!), and so this one little sentence may add a tremendous amount of work. I hope that I am interpreting this wrong, and I wanted to find out what others were doing.
Thanks in Advance,
Skip
 
vladimir levin
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My interpretation is that your client has to be able to
supply all the functionality defined in the Data class.
I'm not sure why this adds all that much work even if you're
using sockets. You just need to include have an instruction
defined in your protocol for each of these actions (eg. add,
delete, find, etc..).
Vlad
 
Skip Cole
Ranch Hand
Posts: 177
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I guess it depends on what one's definition of 'a lot' of extra effort is.
To me it seems like a lot, since I have to expose methods in 3 different places (my database singleton, my database server, my client) for 14 different methods:
add
close
criteriaFind
Data
Data
delete
find
getFieldInfo
getRecord
getRecordCount
getUniqEntries
lock
modify
unlock
This means a minimum of 42 new methods, or roughly 200 more lines of code.
To me this is a lot.
 
Matt DeLacey
Ranch Hand
Posts: 318
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Skip,
I feel very strongly that you have to set it up so that your
GUI COULD use all methods, but you don't have to have it such that they DO. In that sense, of course you don't have to be able to add a record, but you should have support in your serialization in case that wants to be added at anothe time. So, like vladimir was saying you could just have an instruction defined for it but you don't have to write any significant code per se. JUst my $0.02
Matt
 
Skip Cole
Ranch Hand
Posts: 177
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with you, and I am setting up the wrappers to expose the methods.
I guess the only part of this that doesn't sit well with me is that I am going to be exposing some methods to meet the requirement, and never testing this out. Even in the writing of wrappers some things can go wrong, but since there are no corresponding functional requirements, I'm not going to go the extra 100 yards to develope tests for these. (I do after all want to eventually finish this thing :-) )
It is a strange requirement, and not likely one that would come from a client who would be more interested in functionality.
Thanks for your input.
Skip
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic