All I really meant about getting started with the docs, etc., is that it
might make any source-wading easier. When I first looked at Tomcat source I
was quite lost, but when I went through all of the available architecture
stuff, I was then able to very easily drill into the source and find answers
to just exactly the type of question you're asking ("is it a hash map or a
hashtable, or some other type of data structure", etc., "Oh, THAT's what
they mean by interceptor...").
As a side note, I have always believed (from available literature) that most
web-app environments (java, asp, php, or otherwise) provide no
synchronization/protection of any kind for "global" object scopes (session,
application, etc.), and that it is assumed that you treat these entities as
entirely thread-unsafe, unless you serialize your own behavior. Of course,
I could be wrong, but that's the impression I have always gotten across all
the environments I've worked in (which isn't everything under the sun, but
it's plenty of stuff). That's also why it's generally a good idea to
absolutely minimize the amount of stuff jammed into a session or application
scope...gives you less "undefined" behavior to debug. Sounds like you are
already familiar with all this, though.
cheers and good luck
fillup
On 5/26/02 1:23 PM, "jfc100" <[EMAIL PROTECTED]> wrote:
> Phillip Morelock wrote:
>
>> On the TC 3 documentation page there is an excellent "tomcat internals"
>> document....but maybe you already saw that? I myself am a big TC 3 user as
>> well, most of my stuff still runs on that.
>>
>> fillup
>>
>>
>> On 5/26/02 4:11 AM, "jfc100" <[EMAIL PROTECTED]> wrote:
>>
>>> Phillip Morelock wrote:
>>>
>>>> I just quickly checked the site and there are also a couple of "tomcat
>>>> internals" articles and the full javadoc for Tomcat 4 is already posted
>>>> there as well.
>>>>
>>>> /f/
>>>>
>>>> --
>>>>
>>>> Have you built the Tomcat source javadoc tree? Maybe you don't want to
>>>> wade
>>>> knee-deep in source...understandable, I guess. But at least build yourself
>>>> the javadoc from the sources and read that stuff. Also see the high-level
>>>> architecture image (or maybe pdf?) on the jakarta site.
>>>>
>>>> fillup
>>>>
>>>>
>>>>>>> Can someone tell me how tomcat stores session objects or at least where
>>>>>>> I could find out this info without looking at the src?
>>>>>>>
>>>>>> without looking at the source? why not? it's Free, and it's the most
>>>>>> authoritative answer you can get.
>>>>>>
>>>>> Hi,
>>>>>
>>>>> Maybe I just feel like getting someone else's opinion. Because, where
>>>>> reading the src is excellent excercise, you may not find what the
>>>>> general policies are regarding any particular feature. What you will
>>>>> get is a precise picture of what the product does at that specific point
>>>>> in time(or for that specific version). I am trying to establish the
>>>>> broad policies of a servlet engine implementation - the reference
>>>>> implementation. If one was going to produce a document which introduced
>>>>> the product's features I would expect to find this kind of information
>>>>> in it. So if the servlet spec is a bit vague perhaps the document might
>>>>> mention a few implementation details. Not an all-out volume of commentry
>>>>> - just the general approach taken.
>>>>>
>>>>> Seeing as tomcat has undergone a fair bit of development and has been
>>>>> subjected to some structural changes between recent releases(i.e. 3.x vs
>>>>> 4.0), I thought my first port of call might be to find a long suffering
>>>>> fellow tomcat-user who may have passed on a few helpful hints or his/her
>>>>> take on the big picture (or part thereof, even) - just because he can.
>>>>>
>>>>> Can someone point me to a reference / tech article or discussion? Does
>>>>> anyone know whether or not the way the session management is handled by
>>>>> tomcat has changed in any major way? Are there any caveats to accessing
>>>>> session objects from multiple simultaneous requests? The way this is
>>>>> implementated in the reference implementation (between specs) I would
>>>>> have thought would be documented somewhere other than in the src code.
>>>>>
>>>>> Regards
>>>>> Joe
>>>>>
>>>>
>>>> --
>>>> To unsubscribe, e-mail:
>>>> <mailto:[EMAIL PROTECTED]>
>>>> For additional commands, e-mail:
>>>> <mailto:[EMAIL PROTECTED]>
>>>>
>>>>
>>> Thanks for that, Phillip.
>>>
>>> I have downloaded the src-dist for both 3 and 4 versions but have not
>>> yet genned the javadoc - I'll do that when I've looked at the catalina
>>> docs. I was hoping there may be docs prior to tc4 (we are currently on
>>> 3.3) but that is a big help nevertheless. I guess its likely I'll find
>>> out soon the extent of the rewrite.
>>>
>>> Cheers
>>> Joe
>>>
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
>>> <mailto:[EMAIL PROTECTED]>
>>> For additional commands, e-mail:
>>> <mailto:[EMAIL PROTECTED]>
>>>
>>
>>
>> --
>> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>>
>>
> yes I briefly looked at it but didn't on the initial parse find anything
> on session management. From what I can gather, there is no
> synchronization provided by tomcat when it comes to accessing sessions
> or session contents. Maybe accessing sessions is a bit of a red herring
> since we are talking about concurrent access within a single session.
> Whichever data structure tc uses for storing the session objects (or
> facades) would probably answer that one. Hastable is synced while
> HashMap anf the others are not.
>
> thanks for your input fillup!
>
> joe
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
