Re: [PHP] Incoming Development
on 19/06/02 9:35 AM, César Aracena ([EMAIL PROTECTED]) wrote: b) An area where the students can read or download books, in order to avoid having to spend so much money in photocopies. That will be illegal :) Everything else sounds good. Start with a decent user/member/login/session system, then work your way up from there. Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Incoming Development
Thanks on the quote. Actually, I am wondering about the legal concern about publishing books in a site like this. It comes to my mind, that if only registered students are able to search trough this site, it will be just like an open University library. Of course the University would hold at least one hard copy of each book published and written permission of each author/editor. I think of this part as a on-line library of the University... does this make any sense? About the other point, when you say decent what are you suggesting? What would it be stronger and more reliable... a SESSION handler or http authentication??? -Original Message- From: Justin French [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 11:23 PM To: php Subject: Re: [PHP] Incoming Development on 19/06/02 9:35 AM, César Aracena ([EMAIL PROTECTED]) wrote: b) An area where the students can read or download books, in order to avoid having to spend so much money in photocopies. That will be illegal :) Everything else sounds good. Start with a decent user/member/login/session system, then work your way up from there. Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Incoming Development
Each to their own, but I believe sessions will make it easier for you to know who they are from page to page, for example when they post into a forum or ask a question, it's all based on their user id. FWIW, photocopying more than 10% of a book is breech of copyright as well... even if it was in a library, so I don't like your chances. To get started with sessions, I'd look at Kevin Yank's article on sitepoint.com, but it uses cookies, and isn't exactly what you're after, but it's been the basis of my entire session library. Justin French on 19/06/02 12:45 PM, César Aracena ([EMAIL PROTECTED]) wrote: Thanks on the quote. Actually, I am wondering about the legal concern about publishing books in a site like this. It comes to my mind, that if only registered students are able to search trough this site, it will be just like an open University library. Of course the University would hold at least one hard copy of each book published and written permission of each author/editor. I think of this part as a on-line library of the University... does this make any sense? About the other point, when you say decent what are you suggesting? What would it be stronger and more reliable... a SESSION handler or http authentication??? -Original Message- From: Justin French [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 11:23 PM To: php Subject: Re: [PHP] Incoming Development on 19/06/02 9:35 AM, César Aracena ([EMAIL PROTECTED]) wrote: b) An area where the students can read or download books, in order to avoid having to spend so much money in photocopies. That will be illegal :) Everything else sounds good. Start with a decent user/member/login/session system, then work your way up from there. Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Incoming Development
Thanks again for the input. I also like using sessions instead of http auth. I been working with it quite a lot lately, but I still don't know how to do one thing and will need it with something like this. It would help to keep track of each user (what he/she does), in order to make PHP throw statistics for each student I ask it to. I know the basics of relating this with a DB, but the thing is that after the user logs in, the userid used to open that session disappear. For example, if I show the student: echo Welcome userid at the login script, when that student goes to some other page that is does not holds the login script, it would print Hi instead of Hi Whatevername. How can I keep track of this things??? Cookies which I want to avoid??? Again with the copyright matter (and sorry for I want to kill every possibility)... a common mid-career medicine book in Argentina may cost U$S 1.500,00 and a common income here (for a hole family) is around U$S 150,00 top. And it is a Public University... shouldn't be a way for editors to make an exception? Anyway... just 2% aprox of all the students buy books here. -Original Message- From: Justin French [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 11:57 PM To: César Aracena; 'php' Subject: Re: [PHP] Incoming Development Each to their own, but I believe sessions will make it easier for you to know who they are from page to page, for example when they post into a forum or ask a question, it's all based on their user id. FWIW, photocopying more than 10% of a book is breech of copyright as well... even if it was in a library, so I don't like your chances. To get started with sessions, I'd look at Kevin Yank's article on sitepoint.com, but it uses cookies, and isn't exactly what you're after, but it's been the basis of my entire session library. Justin French on 19/06/02 12:45 PM, César Aracena ([EMAIL PROTECTED]) wrote: Thanks on the quote. Actually, I am wondering about the legal concern about publishing books in a site like this. It comes to my mind, that if only registered students are able to search trough this site, it will be just like an open University library. Of course the University would hold at least one hard copy of each book published and written permission of each author/editor. I think of this part as a on-line library of the University... does this make any sense? About the other point, when you say decent what are you suggesting? What would it be stronger and more reliable... a SESSION handler or http authentication??? -Original Message- From: Justin French [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 11:23 PM To: php Subject: Re: [PHP] Incoming Development on 19/06/02 9:35 AM, César Aracena ([EMAIL PROTECTED]) wrote: b) An area where the students can read or download books, in order to avoid having to spend so much money in photocopies. That will be illegal :) Everything else sounds good. Start with a decent user/member/login/session system, then work your way up from there. Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Incoming Development
For example, if I show the student: echo Welcome userid at the login script, when that student goes to some other page that is does not holds the login script, it would print Hi instead of Hi Whatevername. How can I keep track of this things??? Cookies which I want to avoid??? ? Session_start(); $_SESSION['userid'] = $userid; ? Now you have $_SESSION['userid'] on any page you use session_start() on. That's the idea of sessions...passing variables among pages... You use the same technique to make sure a person logged in. When the username and password match, set a session variable like 'logged-in'. On every other page, check for this variable. If it exists, they are logged in, if not, then redirect to the log in page. ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
