(Apr 24, 2012 12:23 PM)ubbelol Wrote: Looks good, but what more is there to it then just MethodInfo.Invoke? ;o
(Apr 25, 2012 02:50 AM)The MammoTh Wrote: Same question as UbbeLol, besides that good job.
Im not that good at explaining in my own language(Dutch) so i am terrible in explaining in english, but i will try it! If you do not understand it, then please read the
source code! Okay here we go:)
The connection is currently secured with AES encryption. Here are the current packetids:
- CreateObject // This will create a new object in the client with an id (This is using ConstructorInfo.Invoke and also BinaryFormatter to serialize and deserialize the parameters)
- InvokeMethod // This will invoke a method in a object created in the client and return the returnvalue as another remoteobject, if the return value is nothing(void) the server will return null as result (This is using MethodInfo.Invoke and also the BinaryFormatter, same reason as CreateObject)
- GetObject // This will serialize the object created by CreateObject or InvokeMethod and send it to the server (This uses BinaryFormatter to serialize and deserialize the object)
- DestroyObject // This will Destroy the object created by the server
- InvokeStaticMethod // This will invoke a static method and return the return value as a new remoteobject (aslo returns null if the return value is null) (This uses the same things as InvokeMethod, the only diffrence is that this is a static method)
There are some more things that you can see for you're self in the
source code, like sending methodinfos to the server, and how the objects are created and destroyed in the client and the server.
(Apr 24, 2012 03:57 PM)Woofable Wrote: May I ask, what theme are you using :>
I'm currently using a theme called
Leaf, you need to
patch some system files to make it work, you can see all of the install instructions in the DeviantArt post!