top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

blocking web sites in opera

+1 vote

I am getting cookies in Opera 12 that I can't delete. Can I just block the site completely by simply entering the url in the hosts file?

posted Sep 2, 2013 by Garima Jain

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
You can always block the sites in your router settings.

1 Answer

+1 vote
answer Sep 3, 2013 by Naveena Garg
what about blocking incoming messages.
A browser request is not an incoming request.  Its an outgoing request.  Block the ability to even get to the site and you cant get a cookie from that site.

It looks like chrome can make cookie exceptions, etc....
Similar Questions
+2 votes

What kind for web forums and discussion sites are on the internet for:
- web designers
- affiliate internet marketers
- web developers
- wordpress developers

+1 vote

As per tomcat's performance tuning doc, 'tcpNoDelay' can be enabled/disabled at connector level.

Is there a programmatic way to set 'tcpNoDelay' to true for web socket connections ? I am using tomcat's proprietary web socket APIs in my application.

I have gone though the API documentation of tomcat's proprietary web socket implementation, I didn't see any API which allows application to override the 'tcpNoDelay' value.

As per doc for "writeTextMessage(CharBuffer msgCb)" of 'WsOutbound', for each write, tomcat flushes the socket buffer and sends the new frame with the buffer passed. Does that mean, flushing of socket buffer gives the same effect of disabling naggle's algorithm ?

+1 vote

I don't know I am getting this kind of add at my bottom of the desktop.
I am unable open the add panel or what is that. I remove that from my Task bar.
please help me It seem I have got malware in my computer.

enter image description here

0 votes

Am new to node.js.In every document i saw node js is nothing but non blocking and event driven.But am still unaware about what is non-blocking & event driven.Can any one please explain about this.

0 votes

I have a questions regarding the Non Blocking API introduced in Tomcat 8. I'm looking at the TestNonBlockingAPI test as an example, specifically the NBReadServlet class.

@WebServlet(asyncSupported = true)
public class NBReadServlet extends TesterServlet {
 private static final long serialVersionUID = 1L;
 public volatile TestReadListener listener;
 protected void service(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
 // step 1 - start async
 AsyncContext actx = req.startAsync();
 actx.addListener(new AsyncListener() {
 // removed for brevity 
 // step 2 - notify on read
 ServletInputStream in = req.getInputStream();
 listener = new TestReadListener(actx);


My question is why does the test call "listener.onDataAvailable()" at the end?

In regards to the "onDataAvailable()" method, Section 3.7 of the spec says…

"The onDataAvailable method is invoked on the ReadListener when data is available to read from the incoming request stream. The container will invoke the method the first time when data is available to read. The container will subsequently invoke the onDataAvailable method if and only if isReady method on ServletInputStream, described below, returns false."

...which leads me to believe that the container should be calling onDataAvailable and not the servlet.

As a side note, my test works if I call "onDataAvailable()" from my test servlet. Otherwise it fails and times out.