Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » RMI
Re: RMI [message #9223 is a reply to message #9222] Sun, 22 April 2007 12:25 Go to previous messageGo to previous message
zsolt is currently offline  zsolt
Messages: 702
Registered: December 2005
Location: Budapest, Hungary
Contributor
class RemotelyCallableClass
{
public:
	RCallback1<int> doSomething;
};

class ClientSide()
{
	RClient<RemotelyCallableClass> client; //some setup needed
	void doSomethingRemotely()
	{
		client.doSomething(33);
	}
};

class ServerSide()
{
public:
	ServerSide()
	{

		server.doSomething <<= THISBACK(OnDoSomething);
		//some setup (IP, port)
	}
	RServer<RemotelyCallableClass> server; 
	void OnDoSomething(int v)
	{
		//some processing on server
	}
};

Of course this is an idea only Smile
RCallback arguments should implement a serializable interface if they are not basic types.
The return value could be handled as a callback on the client side with something like RGate<int, int>.
I don't prefer blocking calls.


Edit: I changed RClient to RServer on server side.

[Updated on: Sun, 22 April 2007 13:07]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: DrawAggData.cpp and internal AggDrawData formats
Next Topic: New hash folding function...
Goto Forum:
  


Current Time: Thu Jun 26 21:02:17 CEST 2025

Total time taken to generate the page: 0.04862 seconds