Hi Rob, Adam et al.
I think that its a good point that Adam could point us in the direction
intended for the book. I know that the "book's target audience is web
developers who will be using Tomcat", but if a more specific one could be
pointed out would be very helpful.
In case that the intended
05:52
Para: [EMAIL PROTECTED]
Asunto: Upcoming Tomcat book...
Hi all,
I will shortly be writing a book for Sams Publishing in a
similar format to
the recently released(and well received) book on Python.
I currently have the task of writing a proposal for content
of the book
e original- De: Adam Fowler [mailto:[EMAIL PROTECTED]] Enviado el: Saturday, March 03, 2001 05:52 Para: [EMAIL PROTECTED] Asunto: Upcoming Tomcat book... Hi all, I will shortly be writing a book for Sams Publishing in a similar format to the recently released(and well received) book on Python. I
Enviado el: Saturday, March 03, 2001 05:52
Para: [EMAIL PROTECTED]
Asunto: Upcoming Tomcat book...
Hi all,
I will shortly be writing a book for Sams Publishing in a
similar format to
the recently released(and well received) book on Python.
I currently have the task of writing a proposal f
One thing I'd like to see in such a book is about how to embed tomcat in
other applications (discuss the pros and cons of EmbededTomcat vs.
regular Tomcat).
Regards, Stefan.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
A couple of things I would like to see in a book (and seems to have never
been covered before):
1. How to structure large servlet applications (Data model).
2. Scalable/fail safe servlet applications.
i.e. Our application is accessing a database of up to 100Gb and we cache all
of our data in
Rob et al.--
LDAP is attractive to me because it's where your regular,
already-being-maintained (LAN, whatever) user database is likely to reside
(Exchange, Notes, whatever, with LDAP interface.)
LDAP supports various password/credential schemes: I don't quite understand
why you can't pump in
Allen,
LDAP is sometimes a viable solution and sometimes not. It's a
direction I am already moving and most of the infrastructure is in
place. The problem is I have 3000+ accounts with legacy passwords.
The LDAP server uses, I believe, a SHA-1 digest for passwords.
Therefore, moving from
Hi all,
I will shortly be writing a book for Sams Publishing in a similar format to
the recently released(and well received) book on Python.
I currently have the task of writing a proposal for content of the book. The
book's target audience is web developers who will be using Tomcat. It will
be
That is a very cool thing ;)
I have been looking on the bookshelves for such a book! If you ever need any help let me know. Here is my email.
[EMAIL PROTECTED]
Ahmed Alawy,
Adam Fowler [EMAIL PROTECTED] wrote:
Hi all,I will shortly be writing a book for Sams Publishing in a similar format
Adam,
It's not really a Tomcat issue, but one of the things that's covered
sometimes poorly and sometimes not at all is thread synchronization.
Unless you're using th SingleThreadModel interface, that's a serious
issue for servlet programming, and unless you're familiar with
threading in
My suggestion would be to use an LDAP database as your authentication
database for your individual users. You can authenticate that person
and then access information about their database access group and the
associated group password, if you set up the LDAP database correctly.
In this way, the
12 matches
Mail list logo
