simpleweb-support — General user and support issues

Re: [Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST

[<nik...@go...>]

Hello Niall,

Friday, September 19, 2008, 1:55:31 AM, you wrote:

> Hi,

> How do you create the WebServerThread? Also, is it possible to send
> some code to demonstrate this.

Did the code snippet for the server not come through? Let me know if
you need the full code (there is not much which I left out...).


> I will take a look. I have tested
> with pretty large files and never seen a problem. Also, what are the JVM arguments you use?

-Xmx512m -Xms512m

We are talking about a file which is 4MB which causes a problem
already. As far as I can tell it looks like the client sends around
16KB and then waits until the server starts reading, the server reads
a few bytees (I think the complete header) and then starts to read a
few more bytes (not sure) and then suddenly craps out.

I spent the last two days figuring out what is going wrong, including
tracing and stepping through the code but haven't found the cause.
Please let me know if you need further details.

Regards,

nik39



-- 
Best regards,
 nik.thirtynine                            mailto:nik.thirtynine

Re: [Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST

[Niall G. <gal...@ya...>]

Hi,

Just to mention, if there is a bug the fix will make it in to the next release, which should be some time next week. I appreciate the feedback.

Regards,
Niall


--- On Thu, 9/18/08, Niall Gallagher <gal...@ya...> wrote:

> From: Niall Gallagher <gal...@ya...>
> Subject: Re: [Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST
> To: "Simple support and user issues" <sim...@li...>
> Date: Thursday, September 18, 2008, 4:55 PM
> Hi,
> 
> How do you create the WebServerThread? Also, is it possible
> to send some code to demonstrate this. I will take a look. I
> have tested with pretty large files and never seen a
> problem. Also, what are the JVM arguments you use?
> 
> Thanks,
> Niall
> 
> 
> --- On Thu, 9/18/08, nik...@go...
> <nik...@go...> wrote:
> 
> > From: nik...@go...
> <nik...@go...>
> > Subject: [Simpleweb-Support] Simpleweb Shutting Down
> Connection Unexpecteadly During HTTP POST
> > To: sim...@li...
> > Date: Thursday, September 18, 2008, 4:45 PM
> > Hi,
> > 
> > I am trying to do a HTTP-POST while attaching a file
> and
> > sending it to
> > an instance of the simpleweb server. Everything works
> fine
> > as long as
> > the attached file is not very large (2k is okay for
> > example) but as
> > soon as I am dealing with larger files (4MB) simpleweb
> > unexpecteadly
> > shuts down the connection without reading the whole
> file.
> > 
> > This is how my client (apache httpclient 3.1) looks
> like:
> > 
> > 
> > === client ===
> > 
> >             HttpClient client = new HttpClient();
> >             PostMethod httppost = new
> > PostMethod("http://localhost:8080/aaa");
> >             File f = new
> File("D:/largefile");
> >             BufferedReader inputStream = null;
> > 
> >             try {
> >                 Part[] parts = {new
> FilePart(f.getName(),
> > f)};
> >                 httppost.setRequestEntity(new
> > MultipartRequestEntity(parts, httppost.getParams()));
> > 
> >                 client.executeMethod(httppost);
> > 
> >                 if (httppost.getStatusCode() ==
> > HttpStatus.SC_OK) {
> >                         InputStream in =
> > httppost.getResponseBodyAsStream();
> >                         inputStream = new
> > BufferedReader(new InputStreamReader(in));
> >                         String line;
> >                     while ((line =
> inputStream.readLine())
> > != null) {
> >                         System.out.println(line);
> >                     }
> >                 } else {
> >                   System.out.println("Unexpected
> > failure: " +
> httppost.getStatusLine().toString());
> >                 }
> >                 } catch (FileNotFoundException e) {
> > ...
> > 
> > === end client ===
> > 
> > The client never gets past the executeMethod since
> while
> > executing the
> > method the server disconnects.
> > 
> > And this is how the (very simple) server looks like:
> > 
> > === server ===
> > 
> >         public static void server() throws Exception {
> >                 Container container = new
> > WebserverThread();
> >                 Connection connection = new
> > SocketConnection(container);
> >                 SocketAddress address = new
> > InetSocketAddress(8080);
> > 
> >                 connection.connect(address);
> > 
> >         }
> >         
> >         public void handle(Request request, Response
> > response) {
> > 
> >         ...
> > 
> >         }
> > 
> > === end server ===
> > 
> > The actual handle method is never invoked because the
> > webserver just
> > closes the connection as described before. I've
> also
> > tried out a HTTP
> > PUT with similar problems.
> > 
> > Any clue what I am doing wrong here?
> > 
> > 
> > Thanks in advance
> > 
> > nik39
> >   
> > 
> > -- 
> > Best regards,
> >  nik.thirtynine                         
> > mailto:nik.thirtynine
> > 
> > 
> >
> -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move
> > Developer's challenge
> > Build the coolest Linux based applications with Moblin
> SDK
> > & win great prizes
> > Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 
> 
>       
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

Re: [Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST

[Niall G. <gal...@ya...>]

Hi,

How do you create the WebServerThread? Also, is it possible to send some code to demonstrate this. I will take a look. I have tested with pretty large files and never seen a problem. Also, what are the JVM arguments you use?

Thanks,
Niall


--- On Thu, 9/18/08, nik...@go... <nik...@go...> wrote:

> From: nik...@go... <nik...@go...>
> Subject: [Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST
> To: sim...@li...
> Date: Thursday, September 18, 2008, 4:45 PM
> Hi,
> 
> I am trying to do a HTTP-POST while attaching a file and
> sending it to
> an instance of the simpleweb server. Everything works fine
> as long as
> the attached file is not very large (2k is okay for
> example) but as
> soon as I am dealing with larger files (4MB) simpleweb
> unexpecteadly
> shuts down the connection without reading the whole file.
> 
> This is how my client (apache httpclient 3.1) looks like:
> 
> 
> === client ===
> 
>             HttpClient client = new HttpClient();
>             PostMethod httppost = new
> PostMethod("http://localhost:8080/aaa");
>             File f = new File("D:/largefile");
>             BufferedReader inputStream = null;
> 
>             try {
>                 Part[] parts = {new FilePart(f.getName(),
> f)};
>                 httppost.setRequestEntity(new
> MultipartRequestEntity(parts, httppost.getParams()));
> 
>                 client.executeMethod(httppost);
> 
>                 if (httppost.getStatusCode() ==
> HttpStatus.SC_OK) {
>                         InputStream in =
> httppost.getResponseBodyAsStream();
>                         inputStream = new
> BufferedReader(new InputStreamReader(in));
>                         String line;
>                     while ((line = inputStream.readLine())
> != null) {
>                         System.out.println(line);
>                     }
>                 } else {
>                   System.out.println("Unexpected
> failure: " + httppost.getStatusLine().toString());
>                 }
>                 } catch (FileNotFoundException e) {
> ...
> 
> === end client ===
> 
> The client never gets past the executeMethod since while
> executing the
> method the server disconnects.
> 
> And this is how the (very simple) server looks like:
> 
> === server ===
> 
>         public static void server() throws Exception {
>                 Container container = new
> WebserverThread();
>                 Connection connection = new
> SocketConnection(container);
>                 SocketAddress address = new
> InetSocketAddress(8080);
> 
>                 connection.connect(address);
> 
>         }
>         
>         public void handle(Request request, Response
> response) {
> 
>         ...
> 
>         }
> 
> === end server ===
> 
> The actual handle method is never invoked because the
> webserver just
> closes the connection as described before. I've also
> tried out a HTTP
> PUT with similar problems.
> 
> Any clue what I am doing wrong here?
> 
> 
> Thanks in advance
> 
> nik39
>   
> 
> -- 
> Best regards,
>  nik.thirtynine                         
> mailto:nik.thirtynine
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

[Simpleweb-Support] Simpleweb Shutting Down Connection Unexpecteadly During HTTP POST

[<nik...@go...>]

Hi,

I am trying to do a HTTP-POST while attaching a file and sending it to
an instance of the simpleweb server. Everything works fine as long as
the attached file is not very large (2k is okay for example) but as
soon as I am dealing with larger files (4MB) simpleweb unexpecteadly
shuts down the connection without reading the whole file.

This is how my client (apache httpclient 3.1) looks like:


=== client ===

            HttpClient client = new HttpClient();
            PostMethod httppost = new PostMethod("http://localhost:8080/aaa");
            File f = new File("D:/largefile");
            BufferedReader inputStream = null;

            try {
                Part[] parts = {new FilePart(f.getName(), f)};
                httppost.setRequestEntity(new MultipartRequestEntity(parts, httppost.getParams()));

                client.executeMethod(httppost);

                if (httppost.getStatusCode() == HttpStatus.SC_OK) {
                        InputStream in = httppost.getResponseBodyAsStream();
                        inputStream = new BufferedReader(new InputStreamReader(in));
                        String line;
                    while ((line = inputStream.readLine()) != null) {
                        System.out.println(line);
                    }
                } else {
                  System.out.println("Unexpected failure: " + httppost.getStatusLine().toString());
                }
                } catch (FileNotFoundException e) {
...

=== end client ===

The client never gets past the executeMethod since while executing the
method the server disconnects.

And this is how the (very simple) server looks like:

=== server ===

        public static void server() throws Exception {
                Container container = new WebserverThread();
                Connection connection = new SocketConnection(container);
                SocketAddress address = new InetSocketAddress(8080);

                connection.connect(address);

        }
        
        public void handle(Request request, Response response) {

        ...

        }

=== end server ===

The actual handle method is never invoked because the webserver just
closes the connection as described before. I've also tried out a HTTP
PUT with similar problems.

Any clue what I am doing wrong here?


Thanks in advance

nik39
  

-- 
Best regards,
 nik.thirtynine                          mailto:nik.thirtynine

Re: [Simpleweb-Support] committing in 4.0.2

[Niall G. <gal...@ya...>]

Hi,

Really? Well if that is the case I will take a look. This should not happen. Also, close should force a call to commit. If this is a bug I will fix it for the next release which will be very soon.

Thanks for the feedback,
Niall


--- On Tue, 9/16/08, Aleksandar Cvijovic <yop...@ya...> wrote:

> From: Aleksandar Cvijovic <yop...@ya...>
> Subject: Re: [Simpleweb-Support] committing in 4.0.2
> To: Sim...@li..., gal...@ya...
> Date: Tuesday, September 16, 2008, 3:11 PM
> It was really fast, thank you,
> 
> Well, I tried once more and...
> 
> When I remove resp.commit() from this code:
>         
> if(req.getMethod().equals("HEAD") || code==204 ||
> code==304){
>             resp.setContentLength(0);
>             resp.commit();
>             resp.close();
>             return;
>          }
> my browser is just waiting for response.
> 
> 
> --- On Tue, 9/16/08, Niall Gallagher
> <gal...@ya...> wrote:
> From: Niall Gallagher <gal...@ya...>
> Subject: Re: [Simpleweb-Support] committing in 4.0.2
> To: Sim...@li...,
> yop...@ya...
> Date: Tuesday, September 16, 2008, 10:21 PM
> 
> Hi,
> 
> For most cases its best to ignore commit. The commit method
> basically commits
> the HTTP header. It does not send anything. The best thing
> to do is just use the
> close() method. Either in the output stream or the
> response. This is sufficient.
> There are very few instances when commit is needed. Its
> typically used when you
> want to forward the response to another service and you
> don't want that
> service to modify the header.
> 
> Niall
> 
> 
> --- On Tue, 9/16/08, Aleksandar Cvijovic
> <yop...@ya...> wrote:
> 
> > From: Aleksandar Cvijovic <yop...@ya...>
> > Subject: [Simpleweb-Support] committing in 4.0.2
> > To: Sim...@li...
> > Date: Tuesday, September 16, 2008, 2:14 PM
> > Hi,
> > 
> > I switched to new version and...
> > 
> > Earlier all worked well with commit() when
> OutputStream is
> > not used at all (content length 0), but now both
> methods
> > must be called (resp.commit(); resp.close();).
> > Is it bug or normal behavior?
> > 
> > >From documentation:
> > "It is important to note that the Response
> controls
> >  the processing of the HTTP pipeline. The next HTTP
> request
> > is 
> >  not processed until the response has committed. The
> > response is
> >  committed once the commit method is invoked if there
> >  is NO content body. Committing with a content body is
> done
> > only if
> >  correct content is given. The OutputStream acts as 
> >  a client and commits the response once the specified
> > content has 
> >  been written to the issued OutputStream."
> > 
> > 
> > 
> > 
> >      
> >
> -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move
> > Developer's challenge
> > Build the coolest Linux based applications with Moblin
> SDK
> > & win great prizes
> > Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

Re: [Simpleweb-Support] committing in 4.0.2

[Aleksandar C. <yop...@ya...>]

It was really fast, thank you,

Well, I tried once more and...

When I remove resp.commit() from this code:
         if(req.getMethod().equals("HEAD") || code==204 || code==304){
            resp.setContentLength(0);
            resp.commit();
            resp.close();
            return;
         }
my browser is just waiting for response.


--- On Tue, 9/16/08, Niall Gallagher <gal...@ya...> wrote:
From: Niall Gallagher <gal...@ya...>
Subject: Re: [Simpleweb-Support] committing in 4.0.2
To: Sim...@li..., yop...@ya...
Date: Tuesday, September 16, 2008, 10:21 PM

Hi,

For most cases its best to ignore commit. The commit method basically commits
the HTTP header. It does not send anything. The best thing to do is just use the
close() method. Either in the output stream or the response. This is sufficient.
There are very few instances when commit is needed. Its typically used when you
want to forward the response to another service and you don't want that
service to modify the header.

Niall


--- On Tue, 9/16/08, Aleksandar Cvijovic <yop...@ya...> wrote:

> From: Aleksandar Cvijovic <yop...@ya...>
> Subject: [Simpleweb-Support] committing in 4.0.2
> To: Sim...@li...
> Date: Tuesday, September 16, 2008, 2:14 PM
> Hi,
> 
> I switched to new version and...
> 
> Earlier all worked well with commit() when OutputStream is
> not used at all (content length 0), but now both methods
> must be called (resp.commit(); resp.close();).
> Is it bug or normal behavior?
> 
> >From documentation:
> "It is important to note that the Response controls
>  the processing of the HTTP pipeline. The next HTTP request
> is 
>  not processed until the response has committed. The
> response is
>  committed once the commit method is invoked if there
>  is NO content body. Committing with a content body is done
> only if
>  correct content is given. The OutputStream acts as 
>  a client and commits the response once the specified
> content has 
>  been written to the issued OutputStream."
> 
> 
> 
> 
>      
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
>
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      



      

Re: [Simpleweb-Support] committing in 4.0.2

[Niall G. <gal...@ya...>]

Hi,

For most cases its best to ignore commit. The commit method basically commits the HTTP header. It does not send anything. The best thing to do is just use the close() method. Either in the output stream or the response. This is sufficient. There are very few instances when commit is needed. Its typically used when you want to forward the response to another service and you don't want that service to modify the header.

Niall


--- On Tue, 9/16/08, Aleksandar Cvijovic <yop...@ya...> wrote:

> From: Aleksandar Cvijovic <yop...@ya...>
> Subject: [Simpleweb-Support] committing in 4.0.2
> To: Sim...@li...
> Date: Tuesday, September 16, 2008, 2:14 PM
> Hi,
> 
> I switched to new version and...
> 
> Earlier all worked well with commit() when OutputStream is
> not used at all (content length 0), but now both methods
> must be called (resp.commit(); resp.close();).
> Is it bug or normal behavior?
> 
> >From documentation:
> "It is important to note that the Response controls
>  the processing of the HTTP pipeline. The next HTTP request
> is 
>  not processed until the response has committed. The
> response is
>  committed once the commit method is invoked if there
>  is NO content body. Committing with a content body is done
> only if
>  correct content is given. The OutputStream acts as 
>  a client and commits the response once the specified
> content has 
>  been written to the issued OutputStream."
> 
> 
> 
> 
>      
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

[Simpleweb-Support] committing in 4.0.2

[Aleksandar C. <yop...@ya...>]

Hi,

I switched to new version and...

Earlier all worked well with commit() when OutputStream is not used at all (content length 0), but now both methods must be called (resp.commit(); resp.close();).
Is it bug or normal behavior?

>From documentation:
"It is important to note that the Response controls
 the processing of the HTTP pipeline. The next HTTP request is 
 not processed until the response has committed. The response is
 committed once the commit method is invoked if there
 is NO content body. Committing with a content body is done only if
 correct content is given. The OutputStream acts as 
 a client and commits the response once the specified content has 
 been written to the issued OutputStream."




      

Re: [Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0

[Niall G. <gal...@ya...>]

Hi,

Do this:

Container container = new MyContainer();
Processor processor = new ContainerProcessor(container, 10);
Connection connection = new SocketConnection(processor);

So, if you like you can wrap the ContainerProcessor in your implementation of the processor. It works like this.


Conection -> Processor -> Container

Hope this helps,
Niall

--- On Mon, 8/18/08, Niels-Ole Gram <no...@c3...> wrote:

> From: Niels-Ole Gram <no...@c3...>
> Subject: Re: [Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0
> To: gal...@ya..., "Simple support and user issues" <sim...@li...>
> Date: Monday, August 18, 2008, 5:50 AM
> Hi Niall,
> 
> Thanks for you fast reply. This will probably solve my
> problem, though I
> have a problem with an already existing Container. My code
> looks like this:
> 
>             Container container = new MyContainer();
>             Connection connection = new
> SocketConnection(container);
>             connection.connect(new
> InetSocketAddress(port));
> 
> This means that I already got a container, which adds a
> couple of headers to
> the reply, but now I would like to add the new processor as
> well. How is
> this accomplished?
> 
> Thanks again.
> 
> 
> Regards,
> A user of Simple
> 
> On Mon, Aug 18, 2008 at 2:15 PM, Niall Gallagher
> <gal...@ya...>wrote:
> 
> > Hi,
> >
> > Ya its still possible to get the client address. Here
> is what to do.
> >
> > public class MyProcessor implements Processor {
> >
> > private Processor processor;
> >
> > public MyProcessor(Processor processor) {
> >   this.processor = processor;
> > }
> >
> > public void process(Pipeline pipeline) throws
> Exception {
> >   Map map = pipeline.getAttributes();
> >   Socket socket = pipeline.getSocket().socket(); //
> get socket
> >   InetAddress address = socket.getInetAddress(); //
> get client address
> >
> >   map.put("myKeyForAddres", address);
> >   processor.process(pipeline); // forward to main
> processor
> > }
> >
> > public void stop() throws Exception {
> >   processor.stop();
> > }
> > }
> >
> > Then with your request you can get.
> >
> > InetAddress address =
> request.getAttributes().get("myKeyForAddress");
> >
> > This kind of attribute passing can also be used for
> handing over SSL
> > certificates, and other connection based properties. I
> will add the
> > getInetAddress as getClientAddress in a future
> release.
> >
> > Regards,
> > Niall
> >
> > --- On Mon, 8/18/08, zwj...@sn...
> <zwj...@sn...>
> > wrote:
> >
> > > From: zwj...@sn...
> <zwj...@sn...>
> > > Subject: [Simpleweb-Support] Missing
> getInetAddress on Request in Simple
> > v4.0
> > > To: sim...@li...
> > > Date: Monday, August 18, 2008, 4:55 AM
> > > Hi,
> > >
> > > Great work on the new version of Simple! I am
> missing the
> > > old method getInetAddress() on Request - how come
> this has
> > > been removed in the new version? Is it possible
> to somehow
> > > get the address of the client requesting a
> resource?
> > >
> > > Thanks.
> > >
> > >
> > > Regards,
> > > A user of Simple
> > >
> > > --------------------------------------
> > > Protect yourself from spam,
> > > use http://sneakemail.com
> > >
> > >
> -------------------------------------------------------------------------
> > > This SF.Net email is sponsored by the Moblin Your
> Move
> > > Developer's challenge
> > > Build the coolest Linux based applications with
> Moblin SDK
> > > & win great prizes
> > > Grand prize is a trip for two to an Open Source
> event
> > > anywhere in the world
> > >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > > _______________________________________________
> > > Simpleweb-Support mailing list
> > > Sim...@li...
> > >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> >
> >
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move
> Developer's
> > challenge
> > Build the coolest Linux based applications with Moblin
> SDK & win great
> > prizes
> > Grand prize is a trip for two to an Open Source event
> anywhere in the world
> >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> >
> 
> 
> 
> -- 
> Med venlig hilsen
> 
> Niels-Ole Gram
> Udviklingschef / CTO
> C3A Medical A/S, Denmark
> 
> Finlandsgade 10
> DK-8200 Aarhus N
> 
> +45 50530302
> no...@c3...
> http://www.c3a.dk/
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

Re: [Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0

[Niels-Ole G. <no...@c3...>]

Hi Niall,

Thanks for you fast reply. This will probably solve my problem, though I
have a problem with an already existing Container. My code looks like this:

            Container container = new MyContainer();
            Connection connection = new SocketConnection(container);
            connection.connect(new InetSocketAddress(port));

This means that I already got a container, which adds a couple of headers to
the reply, but now I would like to add the new processor as well. How is
this accomplished?

Thanks again.


Regards,
A user of Simple

On Mon, Aug 18, 2008 at 2:15 PM, Niall Gallagher
<gal...@ya...>wrote:

> Hi,
>
> Ya its still possible to get the client address. Here is what to do.
>
> public class MyProcessor implements Processor {
>
> private Processor processor;
>
> public MyProcessor(Processor processor) {
>   this.processor = processor;
> }
>
> public void process(Pipeline pipeline) throws Exception {
>   Map map = pipeline.getAttributes();
>   Socket socket = pipeline.getSocket().socket(); // get socket
>   InetAddress address = socket.getInetAddress(); // get client address
>
>   map.put("myKeyForAddres", address);
>   processor.process(pipeline); // forward to main processor
> }
>
> public void stop() throws Exception {
>   processor.stop();
> }
> }
>
> Then with your request you can get.
>
> InetAddress address = request.getAttributes().get("myKeyForAddress");
>
> This kind of attribute passing can also be used for handing over SSL
> certificates, and other connection based properties. I will add the
> getInetAddress as getClientAddress in a future release.
>
> Regards,
> Niall
>
> --- On Mon, 8/18/08, zwj...@sn... <zwj...@sn...>
> wrote:
>
> > From: zwj...@sn... <zwj...@sn...>
> > Subject: [Simpleweb-Support] Missing getInetAddress on Request in Simple
> v4.0
> > To: sim...@li...
> > Date: Monday, August 18, 2008, 4:55 AM
> > Hi,
> >
> > Great work on the new version of Simple! I am missing the
> > old method getInetAddress() on Request - how come this has
> > been removed in the new version? Is it possible to somehow
> > get the address of the client requesting a resource?
> >
> > Thanks.
> >
> >
> > Regards,
> > A user of Simple
> >
> > --------------------------------------
> > Protect yourself from spam,
> > use http://sneakemail.com
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move
> > Developer's challenge
> > Build the coolest Linux based applications with Moblin SDK
> > & win great prizes
> > Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> > https://lists.sourceforge.net/lists/listinfo/simpleweb-support
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
>



-- 
Med venlig hilsen

Niels-Ole Gram
Udviklingschef / CTO
C3A Medical A/S, Denmark

Finlandsgade 10
DK-8200 Aarhus N

+45 50530302
no...@c3...
http://www.c3a.dk/

Re: [Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0

[Niall G. <gal...@ya...>]

Hi,

Ya its still possible to get the client address. Here is what to do.

public class MyProcessor implements Processor {

private Processor processor;

public MyProcessor(Processor processor) {
   this.processor = processor;
}

public void process(Pipeline pipeline) throws Exception {
   Map map = pipeline.getAttributes();
   Socket socket = pipeline.getSocket().socket(); // get socket
   InetAddress address = socket.getInetAddress(); // get client address
  
   map.put("myKeyForAddres", address);
   processor.process(pipeline); // forward to main processor
}

public void stop() throws Exception {
   processor.stop();
}
}

Then with your request you can get.

InetAddress address = request.getAttributes().get("myKeyForAddress");

This kind of attribute passing can also be used for handing over SSL certificates, and other connection based properties. I will add the getInetAddress as getClientAddress in a future release.

Regards,
Niall

--- On Mon, 8/18/08, zwj...@sn... <zwj...@sn...> wrote:

> From: zwj...@sn... <zwj...@sn...>
> Subject: [Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0
> To: sim...@li...
> Date: Monday, August 18, 2008, 4:55 AM
> Hi,
> 
> Great work on the new version of Simple! I am missing the
> old method getInetAddress() on Request - how come this has
> been removed in the new version? Is it possible to somehow
> get the address of the client requesting a resource?
> 
> Thanks.
> 
> 
> Regards,
> A user of Simple
> 
> --------------------------------------
> Protect yourself from spam, 
> use http://sneakemail.com
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

[Simpleweb-Support] Missing getInetAddress on Request in Simple v4.0

[<zwj...@sn...>]

Hi,

Great work on the new version of Simple! I am missing the old method getInetAddress() on Request - how come this has been removed in the new version? Is it possible to somehow get the address of the client requesting a resource?

Thanks.


Regards,
A user of Simple

--------------------------------------
Protect yourself from spam, 
use http://sneakemail.com

Re: [Simpleweb-Support] Simple 4.0 released

[Niall G. <gal...@ya...>]

Hi,

Yes, seems that the issue I was seeing with SSL was down to a bad certificate, everything works fine now.

Niall


--- On Sun, 7/27/08, Jeff Nichols <je...@ne...> wrote:

> From: Jeff Nichols <je...@ne...>
> Subject: Re: [Simpleweb-Support] Simple 4.0 released
> To: gal...@ya..., "Simple support and user issues" <sim...@li...>
> Date: Sunday, July 27, 2008, 4:10 PM
> Hi Niall,
> 
> Looking forward to trying out 4.0.  Is it safe to say the
> SSL issues
> you were having before have been worked out?
> 
> Thanks for the work!
> Jeff
> 
> 
> On Sun, Jul 27, 2008 at 12:02 AM, Niall Gallagher
> <gal...@ya...> wrote:
> > Hi,
> >
> > For anyone interested, 4.0 has been released. There is
> still some optimizations needed and one or two packages that
> have yet to be migrated to the new implementation. However,
> users should notice a considerable performance improvement
> (core now uses NIO) when it comes to persistent HTTP
> connections and usage for Web 2.0 applications.
> >
> > Niall
> >
> >
> > --- On Sat, 7/12/08, Niall Gallagher
> <gal...@ya...> wrote:
> >
> >> From: Niall Gallagher
> <gal...@ya...>
> >> Subject: [Simpleweb-Support] Simple 4.0 alpha
> >> To: sim...@li...
> >> Date: Saturday, July 12, 2008, 9:17 AM
> >> Hi,
> >>
> >> An alpha version of Simple 4.0 has been released.
> This is
> >> pretty much a complete re-implementation of the
> server from
> >> the ground up. The design remains the same,
> however NIO
> >> replaces the previous polling scheduler. Also the
> package
> >> simple.* is now org.simpleframework.*.
> >>
> >> Currently SSL has some issues, however everything
> else
> >> works well. This implementation has greatly
> improved
> >> responsiveness. To download you can visit.
> >>
> >>
> http://simpleweb.sourceforge.net/4.0/package/4.0-alpha/
> >>
> >> Documentation can be found here.
> >>
> >> http://simpleweb.sourceforge.net/4.0/doc/javadoc/
> >>
> >> Niall
> >>
> >>
> >>
> >>
> >>
> -------------------------------------------------------------------------
> >> Sponsored by: SourceForge.net Community Choice
> Awards: VOTE
> >> NOW!
> >> Studies have shown that voting for your favorite
> open
> >> source project,
> >> along with a healthy diet, reduces your potential
> for
> >> chronic lameness
> >> and boredom. Vote Now at
> >> http://www.sourceforge.net/community/cca08
> >> _______________________________________________
> >> Simpleweb-Support mailing list
> >> Sim...@li...
> >>
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> >
> >
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> > Build the coolest Linux based applications with Moblin
> SDK & win great prizes
> > Grand prize is a trip for two to an Open Source event
> anywhere in the world
> >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> >


      

Re: [Simpleweb-Support] Simple 4.0 released

[Jeff N. <je...@ne...>]

Hi Niall,

Looking forward to trying out 4.0.  Is it safe to say the SSL issues
you were having before have been worked out?

Thanks for the work!
Jeff


On Sun, Jul 27, 2008 at 12:02 AM, Niall Gallagher
<gal...@ya...> wrote:
> Hi,
>
> For anyone interested, 4.0 has been released. There is still some optimizations needed and one or two packages that have yet to be migrated to the new implementation. However, users should notice a considerable performance improvement (core now uses NIO) when it comes to persistent HTTP connections and usage for Web 2.0 applications.
>
> Niall
>
>
> --- On Sat, 7/12/08, Niall Gallagher <gal...@ya...> wrote:
>
>> From: Niall Gallagher <gal...@ya...>
>> Subject: [Simpleweb-Support] Simple 4.0 alpha
>> To: sim...@li...
>> Date: Saturday, July 12, 2008, 9:17 AM
>> Hi,
>>
>> An alpha version of Simple 4.0 has been released. This is
>> pretty much a complete re-implementation of the server from
>> the ground up. The design remains the same, however NIO
>> replaces the previous polling scheduler. Also the package
>> simple.* is now org.simpleframework.*.
>>
>> Currently SSL has some issues, however everything else
>> works well. This implementation has greatly improved
>> responsiveness. To download you can visit.
>>
>> http://simpleweb.sourceforge.net/4.0/package/4.0-alpha/
>>
>> Documentation can be found here.
>>
>> http://simpleweb.sourceforge.net/4.0/doc/javadoc/
>>
>> Niall
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> Sponsored by: SourceForge.net Community Choice Awards: VOTE
>> NOW!
>> Studies have shown that voting for your favorite open
>> source project,
>> along with a healthy diet, reduces your potential for
>> chronic lameness
>> and boredom. Vote Now at
>> http://www.sourceforge.net/community/cca08
>> _______________________________________________
>> Simpleweb-Support mailing list
>> Sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
>

[Simpleweb-Support] Simple 4.0 released

[Niall G. <gal...@ya...>]

Hi,

For anyone interested, 4.0 has been released. There is still some optimizations needed and one or two packages that have yet to be migrated to the new implementation. However, users should notice a considerable performance improvement (core now uses NIO) when it comes to persistent HTTP connections and usage for Web 2.0 applications.

Niall


--- On Sat, 7/12/08, Niall Gallagher <gal...@ya...> wrote:

> From: Niall Gallagher <gal...@ya...>
> Subject: [Simpleweb-Support] Simple 4.0 alpha
> To: sim...@li...
> Date: Saturday, July 12, 2008, 9:17 AM
> Hi,
> 
> An alpha version of Simple 4.0 has been released. This is
> pretty much a complete re-implementation of the server from
> the ground up. The design remains the same, however NIO
> replaces the previous polling scheduler. Also the package
> simple.* is now org.simpleframework.*.
> 
> Currently SSL has some issues, however everything else
> works well. This implementation has greatly improved
> responsiveness. To download you can visit.
> 
> http://simpleweb.sourceforge.net/4.0/package/4.0-alpha/
> 
> Documentation can be found here.
> 
> http://simpleweb.sourceforge.net/4.0/doc/javadoc/
> 
> Niall
> 
> 
>       
> 
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE
> NOW!
> Studies have shown that voting for your favorite open
> source project,
> along with a healthy diet, reduces your potential for
> chronic lameness
> and boredom. Vote Now at
> http://www.sourceforge.net/community/cca08
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


      

[Simpleweb-Support] Simple 4.0 alpha

[Niall G. <gal...@ya...>]

Hi,

An alpha version of Simple 4.0 has been released. This is pretty much a complete re-implementation of the server from the ground up. The design remains the same, however NIO replaces the previous polling scheduler. Also the package simple.* is now org.simpleframework.*.

Currently SSL has some issues, however everything else works well. This implementation has greatly improved responsiveness. To download you can visit.

http://simpleweb.sourceforge.net/4.0/package/4.0-alpha/

Documentation can be found here.

http://simpleweb.sourceforge.net/4.0/doc/javadoc/

Niall


      

Re: [Simpleweb-Support] How to use https with simpleframework

[Niall G. <gal...@ya...>]

Hi,

Just create a javax.net.SSLServerSocket instead of a
java.net.ServerSocket. This will use SSL and HTTP will
be used as normal. There are plenty of tutorials on
how to use the SSLServerSocket.

Niall


--- Dmitry Kudrenko <in...@ar...> wrote:

> Greetings,
> 
> I have an application based on simpleframework. I am
> using http
> protocol to access for my application. But now I
> should change it to
> https. I assume it is easy, but unfortunately I
> didn't find this
> information in the documentation. I am novice in
> simpleframewrk, can
> somebody advice me how to use https instead of http,
> and is it
> possible without changing a code?
> 
> Thank you in advance.
> 
> -- 
> Best regards,
> Dmitry Kudrenko
> ARDAS group (http://www.ardas.dp.ua)
> 
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008
> JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still
> time to save $100. 
> Use priority code J8TL2D2. 
>
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
>
https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Simpleweb-Support] How to use https with simpleframework

[Dmitry K. <in...@ar...>]

Greetings,

I have an application based on simpleframework. I am using http
protocol to access for my application. But now I should change it to
https. I assume it is easy, but unfortunately I didn't find this
information in the documentation. I am novice in simpleframewrk, can
somebody advice me how to use https instead of http, and is it
possible without changing a code?

Thank you in advance.

-- 
Best regards,
Dmitry Kudrenko
ARDAS group (http://www.ardas.dp.ua)

Re: [Simpleweb-Support] LeaseMonitor problem

[Anton <ant...@ar...>]

Thank you for your reply, Niall.
It seems that ReactiveQueue needs constant data as a contract priority 
to work correctly but uses dynamic one in truth. Its because of the 
priority (lease duration) is changed every moment but it has calculated 
only once before adding to the queue.
I think the queue should use the real time of contract expiry as a 
priority instead of lease duration.

I looked to the LeaseScheduler class to see the mechanism of contract 
adding to the queue.  I think, the problem could be solved by modifying 
"process" method:
I change:
    long wait = lease.getExpiry();
to:
    long wait = lease.getExpiry() + new Date().getTime();

So, now the queue has constant data as a priority. It works for me. The 
result of my previous test became:

Clean method starts for:
   - User1 after 15000 ms;
   - User2 after 15000 ms;
   - User3 after 13000 ms.

instead of:

Clean method starts for:
   - User1 after 15000 ms;
   - User2 after 25000 ms;
   - User3 after 13000 ms.

What do you think?

Thank you.
> Hi,
>
> Ill take a look at this. I have currently refactored
> this framework so it should be a little more
> responsive. I think this could be down to the
> PriorityQueue used.
>
> Thanks,
> Niall
>
> --- Anton <ant...@ar...> wrote:
>
>   
>> Greetings,
>>
>> I use simple-core-3.1.3 as an engine for my web
>> application. It includes 
>> Lease mechanism. And it works incorrectly for me.
>> Sometimes, I have the 
>> following issue: I scheduled events for some time
>> (ex: 6000 ms) but it 
>> invokes 'clean' later than it should be (ex: 20000
>> ms). CPU usage can't 
>> be a reason.
>>
>> I wrote a simple test to check lease mechanism:
>>
>> public class CleanerTester implements Cleaner{
>>    ...
>>    public void test() {
>>        LeaseManager leaseManager = new
>> LeaseManager(this);
>>        leaseManager.lease("user1", 15000);
>>        leaseManager.lease("user2", 15000);
>>        Thread.sleep(12000);
>>        leaseManager.lease("user3", 13000);
>>         ...
>>    }
>>
>>    public void clean(String user) {
>>        ...
>>    }
>> }
>>
>> The result was:
>> Clean method starts for:
>>    - User1 after 15000 ms;
>>    - User2 after 25000 ms;
>>    - User3 after 13000 ms.
>>
>> User2 was processed only when User3 is completed.
>>
>> I studied the source code. There is a ReactiveQueue
>> for keeping active 
>> contracts. It seems that queue priority mechanism
>> works incorrectly for 
>> incoming ones. For my example:
>>
>> [00:00:00,000] User1 contract was added to the queue
>>                        1) data = user1, value=-15000
>> [00:00:00,000] User2 contract was added to the queue
>>                        1) data = user1, value=-15000
>>                        2) data = user2, value=-15000
>> [00:00:00,000] User1 as a most priority contract was
>> removed from queue 
>> for processing
>>                        1) data = user2, value=-15000
>> [00:00:12,000] User3 contract was added to the queue
>>                        1) data = user3, value=-13000
>>                        2) data = user2, value=-15000
>> [00:00:15,000] Clean started for User1. User3 as a
>> most priority 
>> contract was removed from queue for processing
>>                        1) data = user2, value=-15000
>> [00:00:25,000] Clean started for User3. User2 as a
>> most priority 
>> contract was removed from queue for processing
>> [00:00:25,000] Clean started for User2.
>>
>> Is it right?
>>
>> Thanks in advance.
>>
>> Best regards,
>> Anton Grinenko,
>> ARDAS group (http://www.ardas.dp.ua)
>>     
Best regards,
Anton Grinenko,
ARDAS group (http://www.ardas.dp.ua)

Re: [Simpleweb-Support] LeaseMonitor problem

[Niall G. <gal...@ya...>]

Hi,

Ill take a look at this. I have currently refactored
this framework so it should be a little more
responsive. I think this could be down to the
PriorityQueue used.

Thanks,
Niall

--- Anton <ant...@ar...> wrote:

> Greetings,
> 
> I use simple-core-3.1.3 as an engine for my web
> application. It includes 
> Lease mechanism. And it works incorrectly for me.
> Sometimes, I have the 
> following issue: I scheduled events for some time
> (ex: 6000 ms) but it 
> invokes 'clean' later than it should be (ex: 20000
> ms). CPU usage can't 
> be a reason.
> 
> I wrote a simple test to check lease mechanism:
> 
> public class CleanerTester implements Cleaner{
>    ...
>    public void test() {
>        LeaseManager leaseManager = new
> LeaseManager(this);
>        leaseManager.lease("user1", 15000);
>        leaseManager.lease("user2", 15000);
>        Thread.sleep(12000);
>        leaseManager.lease("user3", 13000);
>         ...
>    }
> 
>    public void clean(String user) {
>        ...
>    }
> }
> 
> The result was:
> Clean method starts for:
>    - User1 after 15000 ms;
>    - User2 after 25000 ms;
>    - User3 after 13000 ms.
> 
> User2 was processed only when User3 is completed.
> 
> I studied the source code. There is a ReactiveQueue
> for keeping active 
> contracts. It seems that queue priority mechanism
> works incorrectly for 
> incoming ones. For my example:
> 
> [00:00:00,000] User1 contract was added to the queue
>                        1) data = user1, value=-15000
> [00:00:00,000] User2 contract was added to the queue
>                        1) data = user1, value=-15000
>                        2) data = user2, value=-15000
> [00:00:00,000] User1 as a most priority contract was
> removed from queue 
> for processing
>                        1) data = user2, value=-15000
> [00:00:12,000] User3 contract was added to the queue
>                        1) data = user3, value=-13000
>                        2) data = user2, value=-15000
> [00:00:15,000] Clean started for User1. User3 as a
> most priority 
> contract was removed from queue for processing
>                        1) data = user2, value=-15000
> [00:00:25,000] Clean started for User3. User2 as a
> most priority 
> contract was removed from queue for processing
> [00:00:25,000] Clean started for User2.
> 
> Is it right?
> 
> Thanks in advance.
> 
> Best regards,
> Anton Grinenko,
> ARDAS group (http://www.ardas.dp.ua)
> 
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008
> JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still
> time to save $100. 
> Use priority code J8TL2D2. 
>
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
>
https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Simpleweb-Support] LeaseMonitor problem

[Anton <ant...@ar...>]

Greetings,

I use simple-core-3.1.3 as an engine for my web application. It includes 
Lease mechanism. And it works incorrectly for me. Sometimes, I have the 
following issue: I scheduled events for some time (ex: 6000 ms) but it 
invokes 'clean' later than it should be (ex: 20000 ms). CPU usage can't 
be a reason.

I wrote a simple test to check lease mechanism:

public class CleanerTester implements Cleaner{
   ...
   public void test() {
       LeaseManager leaseManager = new LeaseManager(this);
       leaseManager.lease("user1", 15000);
       leaseManager.lease("user2", 15000);
       Thread.sleep(12000);
       leaseManager.lease("user3", 13000);
        ...
   }

   public void clean(String user) {
       ...
   }
}

The result was:
Clean method starts for:
   - User1 after 15000 ms;
   - User2 after 25000 ms;
   - User3 after 13000 ms.

User2 was processed only when User3 is completed.

I studied the source code. There is a ReactiveQueue for keeping active 
contracts. It seems that queue priority mechanism works incorrectly for 
incoming ones. For my example:

[00:00:00,000] User1 contract was added to the queue
                       1) data = user1, value=-15000
[00:00:00,000] User2 contract was added to the queue
                       1) data = user1, value=-15000
                       2) data = user2, value=-15000
[00:00:00,000] User1 as a most priority contract was removed from queue 
for processing
                       1) data = user2, value=-15000
[00:00:12,000] User3 contract was added to the queue
                       1) data = user3, value=-13000
                       2) data = user2, value=-15000
[00:00:15,000] Clean started for User1. User3 as a most priority 
contract was removed from queue for processing
                       1) data = user2, value=-15000
[00:00:25,000] Clean started for User3. User2 as a most priority 
contract was removed from queue for processing
[00:00:25,000] Clean started for User2.

Is it right?

Thanks in advance.

Best regards,
Anton Grinenko,
ARDAS group (http://www.ardas.dp.ua)

Re: [Simpleweb-Support] Availability of next version

[Jerome L. <co...@no...>]

Hi Niall,

Thanks for the update. I'm looking forward to playing with Simple 4.0. =
Is
the code already available in your SVN repository? If we can help with =
tests
let me know.

Good luck for the final release steps!

Best regards,
Jerome =20

> -----Message d'origine-----
> De : sim...@li...=20
> [mailto:sim...@li...] De=20
> la part de Niall Gallagher
> Envoy=E9 : dimanche 13 janvier 2008 16:46
> =C0 : Simple support and user issues
> Objet : Re: [Simpleweb-Support] Availability of next version
>=20
> Hi Jerome,
>=20
> Well I have pretty much written 4.0, however its been
> difficult to get the time to complete the release. I
> have been working on it recently, and there is not
> much more to do to complete the release.
>=20
> Regards,
> Niall
>=20
> --- Jerome Louvel <co...@no...> wrote:
>=20
> >=20
> > Hi Niall,
> >=20
> > First, let me wish you a happy year 2008 to you and
> > all Simple users!=20
> >=20
> > Thanks to Simple's small footprint, we tend to
> > recommend Simple as a good
> > default connector for Restlet [1].=20
> >=20
> > However, some users have recently complained [2],
> > sometimes loudly [3],
> > about the lack of graceful shutdown in Simple.
> >=20
> > Therefore, I'm wondering when you plan to address
> > this issue, and whether it
> > will be as an update to Simple 3.1 or as a new
> > major/minor release.
> >=20
> > Best regards,
> > Jerome
> >=20
> > [1]
> >
> http://www.restlet.org/documentation/1.1/connectors#simple
> > [2]
> >
> http://restlet.tigris.org/servlets/BrowseList?list=3Ddiscuss&by=3D
> thread&from=3D62
> > 9652
> > [3]
> >
> http://restlet.tigris.org/servlets/ReadMsg?list=3Ddiscuss&msgNo=3D3870
> >=20
> >=20
> >
> --------------------------------------------------------------
> -----------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> >
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n
> et/marketplace
> > _______________________________________________
> > Simpleweb-Support mailing list
> > Sim...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> >=20
>=20
>=20
>=20
>      =20
> ______________________________________________________________
> ______________________
> Looking for last minute shopping deals? =20
> Find them fast with Yahoo! Search. =20
> =
http://tools.search.yahoo.com/newsearch/category.php?category=3Dshopping
>=20
> --------------------------------------------------------------
> -----------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n
> et/marketplace
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support

Re: [Simpleweb-Support] Availability of next version

[Niall G. <gal...@ya...>]

Hi Jerome,

Well I have pretty much written 4.0, however its been
difficult to get the time to complete the release. I
have been working on it recently, and there is not
much more to do to complete the release.

Regards,
Niall

--- Jerome Louvel <co...@no...> wrote:

> 
> Hi Niall,
> 
> First, let me wish you a happy year 2008 to you and
> all Simple users! 
> 
> Thanks to Simple's small footprint, we tend to
> recommend Simple as a good
> default connector for Restlet [1]. 
> 
> However, some users have recently complained [2],
> sometimes loudly [3],
> about the lack of graceful shutdown in Simple.
> 
> Therefore, I'm wondering when you plan to address
> this issue, and whether it
> will be as an update to Simple 3.1 or as a new
> major/minor release.
> 
> Best regards,
> Jerome
> 
> [1]
>
http://www.restlet.org/documentation/1.1/connectors#simple
> [2]
>
http://restlet.tigris.org/servlets/BrowseList?list=discuss&by=thread&from=62
> 9652
> [3]
>
http://restlet.tigris.org/servlets/ReadMsg?list=discuss&msgNo=3870
> 
> 
>
-------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
>
https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[Simpleweb-Support] Availability of next version

[Jerome L. <co...@no...>]

Hi Niall,

First, let me wish you a happy year 2008 to you and all Simple users! 

Thanks to Simple's small footprint, we tend to recommend Simple as a good
default connector for Restlet [1]. 

However, some users have recently complained [2], sometimes loudly [3],
about the lack of graceful shutdown in Simple.

Therefore, I'm wondering when you plan to address this issue, and whether it
will be as an update to Simple 3.1 or as a new major/minor release.

Best regards,
Jerome

[1] http://www.restlet.org/documentation/1.1/connectors#simple
[2]
http://restlet.tigris.org/servlets/BrowseList?list=discuss&by=thread&from=62
9652
[3] http://restlet.tigris.org/servlets/ReadMsg?list=discuss&msgNo=3870

Re: [Simpleweb-Support] Folded headers

[Niall G. <gal...@ya...>]

Hi,

This may be the case. Currently I have refactored this
method, and unit tested it also. The problem will not
appear in the next release.

Niall

--- Richard Begg <Ric...@se...> wrote:

> Hi
> 
> I am using a JBoss SAAJ client making requests in a
> simpleweb server.
> The requests are multipart and the content-type is a
> folded value.
> 
> In my simple service when I inspect the headers it
> would seem the
> content-type header is truncated by several
> characters.  I have used a
> 'packet sniffer' and the actual requests contains
> the correct
> information.  Taking a look at the simpleweb code it
> would seem the
> request header parsing is deficient in respect to
> folded values.  I
> believe the value method in the HeaderParser class
> should be changed to:
> 
>    private void value() {
>       whitespace();  
>       value.off = off;
>       value.len = 0;
>         
>       for(int mark= 0; count < len;){
>          if(terminal(buf[off])) {  /* CR  or  LF */
> >           for(int i = 1; count < len; i++){
>                if(buf[off] == 10) {
>                   count++;  /* skip the LF */
>                   off++;                  
>                   if(space(buf[off])) {
>                      value.len += i;  /* acount for
> bytes examined */
> 
> >                    mark += i;
>                      break; /* folding line */
>                   } 
>                   return; /* not a folding line */
>                } 
>                count++;
>                off++;
>             }       
>          } else {
>             if(!space(buf[off])){
>                value.len= ++mark;
>             } else {
>                mark++;
>             }
>             count++;
>             off++;   
>          }
>       }                
>    }
> 
> NB The lines prefixed with > have changed.  
> 
> Prior to the change the value token length was only
> temporarily
> increased as the next line would overwrite it with
> the value from
> 'mark'.  With this change mark is also increased to
> take into account
> the bytes examined and the count of bytes examined
> starts from 1 instead
> of 0.
> 
> Can you tell me whether my change is valid?
> 
> Cheers,
> Rich.
> 
>
-------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
>
https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ