Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A server can not be initialized with a private encodeable factory #2662

Open
1 of 5 tasks
mregen opened this issue Jun 28, 2024 · 0 comments
Open
1 of 5 tasks

A server can not be initialized with a private encodeable factory #2662

mregen opened this issue Jun 28, 2024 · 0 comments

Comments

@mregen
Copy link
Contributor

mregen commented Jun 28, 2024

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

The server is initialized with a reference to the global factory. If someone add to the globalfactory (e.g. the server has custom types) a client in the same process is already aware of the types and refuses to load them by the complex type system, effectively not creating a private instance.

Expected Behavior

one or multiple servers and clients can use their private copy the encodeable factory

Steps To Reproduce

No response

Environment

- OS:
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

No response

@mregen mregen changed the title A server can not be initialized with a private encodeable factory<title> A server can not be initialized with a private encodeable factory Jun 28, 2024
@mregen mregen added this to the June Update milestone Jun 28, 2024
@mregen mregen modified the milestones: August Update, Oktober Update Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants