I can't speak for everyone, but to me such posts alway seem selfish, and I'm probably
less inclined to answer such a post if I am short of time and have to choose.
The best ways to get an answer are:
1. Give the post an approriate and detailed title. If the title means nothing, nobody may ever read the post. The title of this
thread is OK, "need help URGENT!!" is bad.
2. Take the time to write coherently and correctly. Five minutes spent on phrasing, grammar and spelling might mean ten useful answers instead of just a load of frustrating misunderstandings. Don't use abbreviations (especially ones like "ur" for "you are" or "your", or "smbd" for "somebody") they serve no purpose and may confuse or put off the one person who has the answer you are looking for.
3. Ask as specific and detailed a question as you can. Don't just say "I have a problem with
Tomcat and Servlets" (or even worse, "pblm with tomcat servelets"), explain the problem: what you are trying to achieve, what you have already done, what has happened, and why it is different from what you expected.
4. Give
concise code examples where necessary. Including the actual code you have written can often help someone to find the problem straight away, but no one will bother to read something more than about 20 lines long. Spend a few minutes finding the smallest possible code example which demonstrates the problem - you may even find that this solves the problem for you! When you have a short code example,
paste it from your editor so you can be sure that it is character-for-character the same as the code you have been compiling/running. And put it in UBB CODE tags to make it readable.
5. Read and re-read your post before you press "Submit Reply". Check that it is the
best, clearest, most helpful expression of your problem. Edit it until it is.
To summarize: If the aim of a post is to get an answer, urgent or otherwise, then you owe it to yourself to make everything about it as clear and useful to potential answerers as possible. Don't be afraid to edit your post after you've submitted it, if you think it is not as good as it could be.
[This message has been edited by Frank Carver (edited November 06, 2000).]