[novakasss]

I want to ask, for example I have a server and client classes. I have a GUI components in that client class. If I would send to the server whole client object, and then server would modify smth, it will effect original object? Do I need to send it back to the client after modification? Or it will be so called 'alias', when two references refer to the same object, and changes in one object effect another?

[CasiOo]

You will have to send the object back after you've modified it yes

[blackcompe]

If the client and server are running in the same JVM, you can just send a pointer to the object, otherwise, you need serialize the object and exchange it back and forth.

This post has been edited by blackcompe: 30 December 2012 - 06:39 PM

[jon.kiparsky]

Think about how aliasing happens: two pointers refer to the same location in memory.

Can this happen across a remote connection?

[pbl]

No, not the same JVM.
But I wonder how blackcompe would exchange the Object pointer between the Client and the Server even if they run on the same JVM ?

[blackcompe]

Quote

No, not the same JVM.
But I wonder how blackcompe would exchange the Object pointer between the Client and the Server even if they run on the same JVM ?

Huh? Client and Server classes running in the same JVM instance, sharing the same memory, can't pass references?

[pbl]

How ???
Would like to see a code snippet about that
A few lines will do blackcompe

[blackcompe]

Quote

How ???
Would like to see a code snippet about that
A few lines will do blackcompe

I don't you understand what I said. Note that I never implied anything about sockets being used.

Spoiler

public class Main
{
     public static void main(String[] args)
     {
          new Client().run();
     }
}
 
class Client {
     void run() {
          Msg m = new Msg();
          new Server().send(m);
          System.out.println(m.prop);
     }
}
 
class Server {
     void send(Msg msg) {
          msg.prop = "modified";
     }
}
class Msg {
     String prop;
}

This post has been edited by blackcompe: 31 December 2012 - 07:13 PM

[pbl]

I don't buy that
Completly false assesment -1 all the way

[blackcompe]

Quote

I don't buy that
Completly false assesment -1 all the way

What are you talking about? Nonsense pbl. Complete nonsense!?!?!

[pbl]

What you claim is
Show me an example of a Client and a Server using the same JVM and I'll +1 you for the rest of my life

[extremeblueness]

blackcompe, on 01 January 2013 - 12:38 AM, said:

Quote

How ???
Would like to see a code snippet about that
A few lines will do blackcompe

I don't you understand what I said. This is what I said. Note that I never implied anything about sockets being used.

Where on earth do you get sockets from? He's asking for a code snippet- a small piece of your code. I think it seems perfectly reasonable.

[blackcompe]

Quote

What you claim is
Show me an example of a Client and a Server using the same JVM and I'll +1 you for the rest of my life

But you're mistaken in thinking a client/server architecture can only be applied to networking. It's a general concept. Yes, the OP may have been talking that networking, but he didn't explicitly say it and neither did I. I'm really saying you can pass a message to any object, where the object can modify it without having to pass it back. Interpret it how you want...

This post has been edited by blackcompe: 31 December 2012 - 07:12 PM

[pbl]

You are completly eluding the question
You claimed that a Client/Server architecture can have Client and a Server running inside the same JVM into which a Client (or a Server) sends to the other one a pointer to an object that the other one can modify... so it will be modified in both application

I asked you to show me an example using a few (preferably) lines of code. You failed on providing this example

[jon.kiparsky]

I'm with blackcompe on this one. I don't really see a lot of use cases for it, but there's nothing odd about passing references when you're on the same machine.

But in fact, if we need a use case, here's one: at my office, the linux team is replacing desktop linux machines with virtual machines on a server. It's not too hard to imagine a slightly different configuration, in which we return to the original multiuser arrangement that Unix was designed for. In that case, it would be perfectly reasonable to write a chat client for communication on the local machine, and to pass client objects around on that machine. This would work more or less as blackcompe described, and it would be a good design for that purpose.


EDIT: came in a little late, but here's your example, pbl. I think I get +1 forever, no?

This post has been edited by jon.kiparsky: 31 December 2012 - 07:20 PM