From: Alistair Y. <ali...@sm...> - 2006-07-21 14:26:22
|
oh dear, I've just started on a HelloWorldFacility with javadocs and full documentation before it morphs into a chat tool. So a Facility is registered (hard coded) into Resource? hmmm I need an id for it. The first free one we have here is 301. This be ok for everyone else? or is that taken in other versions of bod? Or is this not a good way to choose? Seems there are random numbers all over the shop. Alistair |
From: Matthew B. <mat...@ou...> - 2006-07-24 08:52:12
|
Alistair Young wrote: > oh dear, I've just started on a HelloWorldFacility with javadocs and > full documentation before it morphs into a chat tool. So a Facility > is registered (hard coded) into Resource? hmmm A resource has a HttpFacilityUINumber which then gets mapped to a facility. The mapping from the number can be changed at deploy time through the Bodington properties file. > I need an id for it. The first free one we have here is 301. This be > ok for everyone else? or is that taken in other versions of bod? We don't have 301 in use. > Or is this not a good way to choose? Seems there are random numbers > all over the shop. There was some plan whereby each major partner would have a chunk of the Facility numbers but I can't remember which chunks we all got. http://sourceforge.net/mailarchive/message.php?msg_id=12464769 Seems to indicate Oxford would use 101-200 and UHI would use 201-300. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
From: Andrew B. <a.g...@le...> - 2006-07-24 09:06:24
|
300-303 are used for the PeerMarker resources. Aggie -----Original Message----- From: bod...@li... [mailto:bod...@li...] On Behalf Of Matthew Buckett Sent: 24 July 2006 09:52 To: Bodington developers Subject: Re: [Bodington-developers] HelloWorld negotiation Alistair Young wrote: > oh dear, I've just started on a HelloWorldFacility with javadocs and > full documentation before it morphs into a chat tool. So a Facility > is registered (hard coded) into Resource? hmmm A resource has a HttpFacilityUINumber which then gets mapped to a facility. The mapping from the number can be changed at deploy time through the Bodington properties file. > I need an id for it. The first free one we have here is 301. This be > ok for everyone else? or is that taken in other versions of bod? We don't have 301 in use. > Or is this not a good way to choose? Seems there are random numbers > all over the shop. There was some plan whereby each major partner would have a chunk of the Facility numbers but I can't remember which chunks we all got. http://sourceforge.net/mailarchive/message.php?msg_id=12464769 Seems to indicate Oxford would use 101-200 and UHI would use 201-300. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bodington-developers mailing list Bod...@li... https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Matthew B. <mat...@ou...> - 2006-07-24 09:23:05
|
Andrew Booth wrote: > 300-303 are used for the PeerMarker resources. This has come up before. http://sourceforge.net/mailarchive/message.php?msg_id=12528832 Facility and Resource IDs are completely unrelated. The resource ID is used by the database layer to work out how to map a set of rows in the database to a Java object and the facility No is used to work out how to display a resource over the web. A java object is not always a resource. There has been a convention that they matched but there is no requirement. There will always be more resource IDs than Facility IDs because some objects don't have a facility (events, users, etc). -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
From: Alistair Y. <ali...@sm...> - 2006-07-24 09:39:05
|
>> 300-303 are used for the PeerMarker resources not according to our version of head Aggie! RESOURCE_PEERMARKER = 300 or am I looking in the wrong place again? > Facility and Resource IDs are completely unrelated Facility id? haven't seen any of them! HelloWorldResource.sql: INSERT INTO classes (type, super_type, db_name, table_name, java_class) VALUES(28, 10, null, null, 'org.bodington.server.resources.HelloWorldResource') GO is "28" the Resource ID or the Facility ID then? I presume it's the resource id. so what's the advice if any? is there any way to avoid collisions? e.g. I've just chosen 301 but PeerMarker uses that although it's not defined anywhere. Alistair On 24 Jul 2006, at 10:23, Matthew Buckett wrote: > Andrew Booth wrote: >> 300-303 are used for the PeerMarker resources. > > This has come up before. > > http://sourceforge.net/mailarchive/message.php?msg_id=12528832 > > Facility and Resource IDs are completely unrelated. The resource ID is > used by the database layer to work out how to map a set of rows in the > database to a Java object and the facility No is used to work out > how to > display a resource over the web. A java object is not always a > resource. > > There has been a convention that they matched but there is no > requirement. There will always be more resource IDs than Facility IDs > because some objects don't have a facility (events, users, etc). > > -- > -- Matthew Buckett, VLE Developer > -- Learning Technologies Group, Oxford University Computing Services > -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Alexis O'C. <ale...@ou...> - 2006-07-24 09:47:33
|
Alistair Young wrote: >>> 300-303 are used for the PeerMarker resources > not according to our version of head Aggie! > RESOURCE_PEERMARKER = 300 > or am I looking in the wrong place again? > >> Facility and Resource IDs are completely unrelated > Facility id? haven't seen any of them! > > HelloWorldResource.sql: > INSERT INTO classes (type, super_type, db_name, table_name, java_class) > VALUES(28, 10, null, null, > 'org.bodington.server.resources.HelloWorldResource') > GO > > is "28" the Resource ID or the Facility ID then? I presume it's the > resource id. > > so what's the advice if any? is there any way to avoid collisions? > e.g. I've just chosen 301 but PeerMarker uses that although it's not > defined anywhere. > > Alistair > > My take on the situtation is that if UHI have got facility numbers 201 - 300 and Aggie has 301 - 400, then: Peermarker should probably be bumped upto 301 (from 300). Alistairs HelloWorld facility should take 203, which is the next available number after 202 (Announcements) within the UHI range on bodington HEAD. Alexis |
From: Alistair Y. <ali...@sm...> - 2006-07-24 09:55:51
|
> HelloWorld facility should take 203 concise answer, thanks Alexis! Alistair On 24 Jul 2006, at 10:48, Alexis O'Connor wrote: > Alistair Young wrote: >>>> 300-303 are used for the PeerMarker resources >> not according to our version of head Aggie! >> RESOURCE_PEERMARKER = 300 >> or am I looking in the wrong place again? >> >>> Facility and Resource IDs are completely unrelated >> Facility id? haven't seen any of them! >> >> HelloWorldResource.sql: >> INSERT INTO classes (type, super_type, db_name, table_name, >> java_class) >> VALUES(28, 10, null, null, >> 'org.bodington.server.resources.HelloWorldResource') >> GO >> >> is "28" the Resource ID or the Facility ID then? I presume it's the >> resource id. >> >> so what's the advice if any? is there any way to avoid collisions? >> e.g. I've just chosen 301 but PeerMarker uses that although it's not >> defined anywhere. >> >> Alistair >> >> > > My take on the situtation is that if UHI have got facility numbers > 201 - 300 and Aggie has > 301 - 400, then: > > Peermarker should probably be bumped upto 301 (from 300). > Alistairs HelloWorld facility should take 203, which is the next > available number after > 202 (Announcements) within the UHI range on bodington HEAD. > > Alexis > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Colin T. <col...@ou...> - 2006-07-24 11:06:39
|
I think we need to make a decision before releasing 2.8 whether we're going to keep the mapping between the Facility number and Object ID (to use Matthew's terminology). I think we're at a point where it could be maintained with a little effort, and that will make future code more easily understood (downside is that we have to maintain the mapping in future tools.) The new ones in my Bod installation are: type | table_name ------+----------------------------- 56 | quick_links 59 | log_book_section_hierarchy 60 | log_book_question_hierarchy 105 | web_auth_user 106 | sp_auth_user 300 | peer_mark_papers 301 | peer_mark_questions 302 | peer_mark_responses 303 | peer_mark_results I'd say that the only one that needs changing is 106 | sp_auth_user as that's in the Oxford range. Arguably quick_links should be in either Oxford or UHI's range too... Would changing sp_auth_user cause anyone any headaches? Colin Alistair Young wrote: >>HelloWorld facility should take 203 > > concise answer, thanks Alexis! > > Alistair > > > On 24 Jul 2006, at 10:48, Alexis O'Connor wrote: > > >>Alistair Young wrote: >> >>>>>300-303 are used for the PeerMarker resources >>> >>>not according to our version of head Aggie! >>>RESOURCE_PEERMARKER = 300 >>>or am I looking in the wrong place again? >>> >>> >>>>Facility and Resource IDs are completely unrelated >>> >>>Facility id? haven't seen any of them! >>> >>>HelloWorldResource.sql: >>>INSERT INTO classes (type, super_type, db_name, table_name, >>>java_class) >>> VALUES(28, 10, null, null, >>>'org.bodington.server.resources.HelloWorldResource') >>>GO >>> >>>is "28" the Resource ID or the Facility ID then? I presume it's the >>>resource id. >>> >>>so what's the advice if any? is there any way to avoid collisions? >>>e.g. I've just chosen 301 but PeerMarker uses that although it's not >>>defined anywhere. >>> >>>Alistair >>> >>> >> >>My take on the situtation is that if UHI have got facility numbers >>201 - 300 and Aggie has >>301 - 400, then: >> >>Peermarker should probably be bumped upto 301 (from 300). >>Alistairs HelloWorld facility should take 203, which is the next >>available number after >>202 (Announcements) within the UHI range on bodington HEAD. >> >>Alexis -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
From: Alistair Y. <ali...@sm...> - 2006-07-24 11:17:12
|
> Facility number and Object ID ok, Object ID is Resource ID and is hard coded in Resource.java? Where does Facility number come from? I heard that that's hard coded in the Resource but I can't find any examples. > I think we're at a point where it could be maintained with a little > effort, and that will make > future code more easily understood then that's a ++ from me once we've sorted the IDs, then it's working out what all those methods do, resourceMenuItem, ooh the pain! oh for some javadocs! but there will be once I get the HelloWorldResource working and documented. Alistair On 24 Jul 2006, at 12:06, Colin Tatham wrote: > > I think we need to make a decision before releasing 2.8 whether > we're going to keep the mapping > between the Facility number and Object ID (to use Matthew's > terminology). > I think we're at a point where it could be maintained with a little > effort, and that will make > future code more easily understood (downside is that we have to > maintain the mapping in future tools.) > > The new ones in my Bod installation are: > > type | table_name > ------+----------------------------- > 56 | quick_links > 59 | log_book_section_hierarchy > 60 | log_book_question_hierarchy > 105 | web_auth_user > 106 | sp_auth_user > 300 | peer_mark_papers > 301 | peer_mark_questions > 302 | peer_mark_responses > 303 | peer_mark_results > > I'd say that the only one that needs changing is > > 106 | sp_auth_user > as that's in the Oxford range. > > Arguably quick_links should be in either Oxford or UHI's range too... > > > Would changing sp_auth_user cause anyone any headaches? > > Colin > > > > > Alistair Young wrote: >>> HelloWorld facility should take 203 >> >> concise answer, thanks Alexis! >> >> Alistair >> >> >> On 24 Jul 2006, at 10:48, Alexis O'Connor wrote: >> >> >>> Alistair Young wrote: >>> >>>>>> 300-303 are used for the PeerMarker resources >>>> >>>> not according to our version of head Aggie! >>>> RESOURCE_PEERMARKER = 300 >>>> or am I looking in the wrong place again? >>>> >>>> >>>>> Facility and Resource IDs are completely unrelated >>>> >>>> Facility id? haven't seen any of them! >>>> >>>> HelloWorldResource.sql: >>>> INSERT INTO classes (type, super_type, db_name, table_name, >>>> java_class) >>>> VALUES(28, 10, null, null, >>>> 'org.bodington.server.resources.HelloWorldResource') >>>> GO >>>> >>>> is "28" the Resource ID or the Facility ID then? I presume it's the >>>> resource id. >>>> >>>> so what's the advice if any? is there any way to avoid collisions? >>>> e.g. I've just chosen 301 but PeerMarker uses that although it's >>>> not >>>> defined anywhere. >>>> >>>> Alistair >>>> >>>> >>> >>> My take on the situtation is that if UHI have got facility numbers >>> 201 - 300 and Aggie has >>> 301 - 400, then: >>> >>> Peermarker should probably be bumped upto 301 (from 300). >>> Alistairs HelloWorld facility should take 203, which is the next >>> available number after >>> 202 (Announcements) within the UHI range on bodington HEAD. >>> >>> Alexis > > -- > ____________________________________ > Colin Tatham > VLE Team > Oxford University Computing Services > > http://www.oucs.ox.ac.uk/ltg/vle/ > http://bodington.org > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Matthew B. <mat...@ou...> - 2006-07-24 09:58:51
|
Alistair Young wrote: >>> 300-303 are used for the PeerMarker resources > not according to our version of head Aggie! > RESOURCE_PEERMARKER = 300 > or am I looking in the wrong place again? The constants in Resource can be completly different to the other numbers. It depends how they are used outside the Resource class. >> Facility and Resource IDs are completely unrelated > Facility id? haven't seen any of them! > > HelloWorldResource.sql: > INSERT INTO classes (type, super_type, db_name, table_name, java_class) > VALUES(28, 10, null, null, > 'org.bodington.server.resources.HelloWorldResource') > GO > > is "28" the Resource ID or the Facility ID then? I presume it's the > resource id. Yep that is the resource ID as I described in my previous email, but that is a bad term (not all database objects map to a resource). Maybe it should just be Object ID. > > so what's the advice if any? is there any way to avoid collisions? The right way to solve this is to have the mapping determined at deploy time rather than development time. > e.g. I've just chosen 301 but PeerMarker uses that although it's not > defined anywhere. Ok I'll at what I think the state is at the moment: Facility No. - This is numeric number of a facility instance. This is stored against a resource (getHttpFacilityNo()) so that we know which facility to use to display it. This is in the bodington-default.properties file with lines such as: buildingservlet.facility.alias=25,org.bodington.servlet.facilities.AliasFacility with 25 being the Facility No. Object ID. - This is the number that the database layer uses for mapping rows to Java Objects. It is hard coded in the .sql files and ends up in the classes, fields and objects tables. It shouldn't be used outside the database layer(?). Resource Constants. - These are the constants defined in Resource that allow you to check what type of resource you are dealing with. The reason that they exist is because we can't do instanceof checks because lots of resources are different only by which facility handles them. Really these are redundant as you can gain this information from the facility information. The only reason to have them is if we intent to have the same resource handle by different facilities in the same installation of Bodington. I believe that there needs to be no correlation between these numbers but could be wrong. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |