From 36c805cc2f6e1953d8236b6e3ed51c332330a585 Mon Sep 17 00:00:00 2001
From: nathan <nathan@dorkbox.com>
Date: Tue, 1 Sep 2020 09:13:12 +0200
Subject: [PATCH] Renamed class

---
 .../ClassRegistrationIfaceAndImpl.kt          | 68 -------------------
 1 file changed, 68 deletions(-)
 delete mode 100644 src/dorkbox/network/serialization/ClassRegistrationIfaceAndImpl.kt

diff --git a/src/dorkbox/network/serialization/ClassRegistrationIfaceAndImpl.kt b/src/dorkbox/network/serialization/ClassRegistrationIfaceAndImpl.kt
deleted file mode 100644
index f9a771cb..00000000
--- a/src/dorkbox/network/serialization/ClassRegistrationIfaceAndImpl.kt
+++ /dev/null
@@ -1,68 +0,0 @@
-/*
- * Copyright 2020 dorkbox, llc
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package dorkbox.network.serialization
-
-import dorkbox.network.rmi.messages.RmiClientReverseSerializer
-
-/**
- * This is to manage serializing RMI objects across the wire...
- *
- * NOTE:
- *   CLIENT: can never send the iface object, if it's RMI, it will send the java Proxy object instead.
- *   SERVER: can never send the iface object, it will always send the IMPL object instead (because of how kryo works)
- *
- *   **************************
- *   NOTE: This works because we TRICK kryo serialization by changing what the kryo ID serializer is on each end of the connection
- *   **************************
- *
- *   What we do is on the server, REWRITE the kryo ID for the impl so that it will send just the rmi ID instead of the object
- *   on the client, this SAME kryo ID must have this serializer as well, so the proxy object is re-assembled.
- *
- *   Kryo serialization works by inspecting the field VALUE type, not the field DEFINED type... So if you send an actual object, you must
- *   register specifically for the implementation object.
- *
- *
- * To recap:
- *  rmi-client: send proxy -> RmiIfaceSerializer -> network -> RmiIfaceSerializer -> impl object (rmi-server)
- *  rmi-server: send impl -> RmiImplSerializer -> network -> RmiImplSerializer -> proxy object (rmi-client)
- *
- *  During the handshake, if the impl object 'lives' on the CLIENT, then the client must tell the server that the iface ID must use this serializer.
- *  If the impl object 'lives' on the SERVER, then the server must tell the client about the iface ID
- */
-internal class ClassRegistrationIfaceAndImpl(ifaceClass: Class<*>,
-                                             val implClass: Class<*>,
-                                             serializer: RmiClientReverseSerializer) : ClassRegistration(ifaceClass, serializer) {
-
-    override fun register(kryo: KryoExtra) {
-        // have to get the ID for the interface (if it exists)
-        val registration = kryo.classResolver.getRegistration(clazz) // this is ifaceClass, and must match what is defined on the rmi client
-        if (registration != null) {
-            id = registration.id
-
-            // override that registration
-            kryo.register(implClass, serializer, id)
-        } else {
-            // now register the impl class
-            id = kryo.register(implClass, serializer).id
-        }
-        info = "Registered $id -> (RMI) ${implClass.name}"
-    }
-
-    override fun getInfoArray(): Array<Any> {
-        // the info array has to match for the INTERFACE (not the impl!)
-        return arrayOf(id, clazz.name, serializer!!::class.java.name)
-    }
-}