| Re: multiple visitors at the same time [message #182986 is a reply to message #182985] |
Tue, 01 October 2013 10:15   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 9/30/2013 11:37 PM, Michael Vilain wrote:
> In article <tabtkdru0f5g$(dot)1x6bq88mzzryc$(dot)dlg(at)40tude(dot)net>,
> richard <noreply(at)example(dot)com> wrote:
>
>> On Mon, 30 Sep 2013 16:16:23 -0700, Michael Vilain wrote:
>>
>>> In article <39cy6hpu04oe$(dot)18k40zgdny9go$(dot)dlg(at)40tude(dot)net>,
>>> richard <noreply(at)example(dot)com> wrote:
>>>
>>>> I kind of realized i now have another problem to deal with.
>>>> As I have it set up, when a visitor enters, that creates a playlist for
>>>> that visitor.
>>>> What happens when another visitor is online?
>>>> I tried it with both IE and FF at the same time.
>>>> While the list is dffierent, there is no audio in the second browser.
>>>>
>>>> So I figure I will have to give each browser a unique id to the playlist.
>>>> But how?
>>>> Would the server crash with s few thousand visitors online at the same
>>>> time?
>>>>
>>>> The wimpy player can embed the playlist into the html, but their way of
>>>> doing it doesn't allowo me to display the file names unless the gilename
>>>> match exactly.
>>>> that is, I could not show "exodus - henry mancini". I'd have to show
>>>> 65-001mp3 because that's how I have the naming convention set up.
>>>
>>> Look into session ID. When someone comes to your site, they have to
>>> login, yes? Tie the session ID created by php to the username. Use
>>> that to create a unique MD5 hash for a playlist you store under their
>>> username in MySQL.
>>>
>>> You do realize that all this will require sychronizing things and MySQL
>>> (or some other DB that deals with record locking)?
>>
>> At this time, I am not looking at visitors needing to sign up and login.
>> I will look into session id and see if that will help.
>
> Most session IDs without a login aren't sufficiently unique. You'll
> need to have additional criteria to ensure that to machines with the
> same browser and hardware connecting to your server from the same IP
> address are able to be differentiated between the two. That's up to
> you. You sound like you need to do a lot of reading up on this before
> you come up with a viable solution. Publically available stuff without
> first authenticating the user will only get you so far.
>
Incorrect. Sessions don't know anything about logins; it's just data to
them. And the session ID needs to be unique for each visitor, whether
or not they are logged in.
Can you imagine, for instance, a shopping cart where multiple people
share the same session id - and therefore cart? Many sites don't
require any information until it's time to check out.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]