SIMON

In general this would be possible. But how will you indicate which client has lost the connection? You do not have any relation. You just would know: Client with IP XYZ and Port ABC is gone. Sou would have to implement your own relation.

I suggest to use the "unreferenced" mechanism, in combination with the session-pattern: http://dev.root1.de/projects/simon/wiki/Sample_session_pattern

Comments/Remarks??

achristian wrote:

In general this would be possible. But how will you indicate which client has lost the connection? You do not have any relation. You just would know: Client with IP XYZ and Port ABC is gone. Sou would have to implement your own relation.

I suggest to use the "unreferenced" mechanism, in combination with the session-pattern: http://dev.root1.de/projects/simon/wiki/Sample_session_pattern

Comments/Remarks??

How to indicate? About the channel that was disconnected. That should be possible by using MINA.

That was not the correct direction of my question. It's clear that the server is able to know which clients got disconnected.
But how will you establish a relation in your ClosedListener implementation?!

On client side it's easy. You know that you are connected to the server. But the server in general does not know about clients. SIMON has, beside the client's IP and port no information or any relation to the client. So the only information one could pass on the server side to the ClosedListener is the IP and maybe the port of the client. You would have to implement your own session-information/relation anyhow. That's why I suggested the session-pattern.

Maybe you could explain what kind of stuff you would cleanup on lost connection to client?! Maybe I then get the point ... :-)

I use some kind of session pattern like stuff. On login the remoteserver transmits a ManagerAdvisor which can retrieve any "service" on the other side. Since the same client can connect on more than one IP I increment the count for same instances of managers. That count should be decremented on connectionlost or on clean logout and the manager instance should be removed if could reaches 0.

    @Override
    public void login(final IManagerAdvisor managerAdvisor) {
        try {
            managerAdvisorLock.lock();

            final AtomicInteger integer = managerAdvisors.get(managerAdvisor);
            if (integer != null && integer.get() > 1) {
                integer.incrementAndGet();

            } else {
                managerAdvisors.put(managerAdvisor, new AtomicInteger(1));
            }

            final IChannelManager channelManager = managerAdvisor
                    .getManager(IChannelManager.class.getSimpleName());

            channelManager.registerChannelListener(this);

        } finally {
            managerAdvisorLock.unlock();
        }
    }

    @Override
    public void logout(final IManagerAdvisor managerAdvisor) {
        try {
            managerAdvisorLock.lock();

            final AtomicInteger integer = managerAdvisors.get(managerAdvisor);
            if (integer == null) {
                return;
            }

            if (integer.get() > 1) {
                integer.decrementAndGet();

            } else {
                managerAdvisors.remove(managerAdvisor);
            }

            final IChannelManager channelManager = managerAdvisor
                    .getManagerByClassName(IChannelManager.class
                            .getCanonicalName());

            if (channelManager != null) {
                channelManager.removeChannelListener(this);
            }

        } finally {
            managerAdvisorLock.unlock();
        }
    }