Recent changes to feature-requests

Integrate Websocket 6455

Daniel De Leon — Sun, 16 Mar 2014 16:56:29 -0000

'Simple' rocks!

And my new requirements needs Websocket 6455.

Look that is very feasible to add this feature, because 'Simple' currently supports asynchronous responses.

Thank you very much for this project.

Clean shutdown

Anonymous — Sat, 03 Sep 2005 09:50:18 -0000

I know, this has been discussed in the mailing lists, but
I think it's really very annoying thing when embedded
Simple HTTP server is closed and many forlorn threads
remain running without any chance to stop them. I use
Simple as a module in a framework with many other
functionalities and I need to close the module and stop
all associated threads without exiting the JVM. So I
submit this to increase its priority a little bit ;-).

Thanx
Martin Stepanek
abrasax@wo.cz

"JDK5 Concurrency and Thread Pooling" port to java1.4

Christophe Roudet — Wed, 10 Aug 2005 17:31:37 -0000

Just a port of Feature Request id 1255992 "JDK5
Concurrency and Thread Pooling" to java 1.4 using
http://www.mathcs.emory.edu/dcl/util/backport-util-
concurrent/

JDK5 Concurrency and Thread Pooling

Gail Rahn Frederick — Wed, 10 Aug 2005 16:09:56 -0000

Migrate Simpleweb to use the thread management and
concurrency utilities in JDK 5's java.util.concurrency
packages.

Niall, I ported your threading and concurrency
utilities to JDK 5 (see the attached ZIP files). Note
that some objects are now unnecessary (like
simple.util.process.Daemon).

In addition, you could rewrite LeaseScheduler to use a
blocking queue rather than a non-threadsafe queue.
LeaseScheduler uses a non-blocking queue but blocks
around add and remove methods. Your way works, but the
JDK5 way is the new standard.

(In fact, all your concurrency and threading works. I
just think it's safer to use JDK constructs where
available.)

I chose not to change anything except your lowest-level
objects - i.e. anything I couldn't immediately retrofit
for JDK5 concurrency. I did not change any application
logic.

We also made two more changes:

* "kill" methods, methods to stop and restart the HTTP
server. They were added when we were debugging the
stability issues with Simple. (The issues that ended up
being a Linux kernel problem.)

* We added RequestLine.getPath() and setPath() to
manage the path to the HTTP request. It may duplicate
getURI(), in some cases but it met our particular needs
better.

Session expiration notification

Brett Wooldridge — Thu, 14 Apr 2005 06:21:21 -0000

I desparately need session expiration notification! I
am storing things like JDBC connections in the session,
and I would like the opportunity to clean them up.

What is needed is either:

1) A way for me to supply my own implementation of
Session -- possibly one that 'extends' Delegate, and
overrides destroy().

2) Some sort of callback/listener for the session-death.

Honestly, the former would be preferable. It seems
that a great deal of care was taken to implement things
such as StoreFactories, MaintainerFactories, and
ModuleFactories -- but there is no way (that I can see)
to replace substitute the implementations these
factories produce.

It's as if an Inversion of Control pattern was
implemented all the way up to the last inch of the mile
and then left.

implement in C#

Qin DeBu — Thu, 20 May 2004 04:37:46 -0000

Hi
The attachment is that I implement SimpleWeb in C#,
I am new to C#,just learned it in a few weeks.So this
Implemention is dirty and Simple,not Clear.But It Can
Work.
You can download .net framework and run csc *.cs

Qin DeBu

Session support?

Anonymous — Sat, 15 May 2004 15:57:34 -0000

I read it carefully.why not support session?
I think you can implement a simple session and session
replication to support loading balance and cluster.
I has tried to implement it in C#,and it can work well
too.

HTTPS support

Tito Costa — Tue, 27 Apr 2004 17:32:11 -0000

Can I use Simple over SSL/HTTPS?
Thank you
Tito

give name to Daemon thread

Denis Tsyplakov — Thu, 26 Feb 2004 07:21:17 -0000

simple.util.process

public Daemon(ObjectQueue ready){
this.thread = new Thread(this);

this.setName("SimpleWeb Daemon");

this.ready = ready;
thread.start();
}

get number of threads from system property

Denis Tsyplakov — Thu, 26 Feb 2004 06:59:02 -0000

Now:
public final class ProcessQueue extends Observable {

...

static {
engine = new ProcessQueue(20);
}

Proposed:

protected static final int DEFAULT_THREAD_COUNT = 20;

static {
String count_s = System.getProperty (
"simple.util.process.queue.thread.count" ,
DEFAULT_THREAD_COUNT );
int count;
try
{
int count = Integer.parseInt(count_s);
}
catch ( NumberFormatException ex )
{
//use default value
count = DEFAULT_THREAD_COUNT;
}
engine = new ProcessQueue(count);
}