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

Web Page for "The Connection Cache concept" is outdated as of Release 0.11.0 #1186

Closed
1 of 16 tasks
in-fke opened this issue Nov 3, 2023 · 4 comments
Closed
1 of 16 tasks
Assignees
Labels

Comments

@in-fke
Copy link

in-fke commented Nov 3, 2023

What happened?

The page https://plc4x.apache.org/users/tools/connection-cache.html no longer reflects the new cache implementation.
And: how do you "dispose" all connections, e.g. for "shutdown" ?

Version

v0.11.0

Programming Languages

  • plc4j
  • plc4go
  • plc4c
  • plc4net

Protocols

  • AB-Ethernet
  • ADS /AMS
  • BACnet/IP
  • CANopen
  • DeltaV
  • DF1
  • EtherNet/IP
  • Firmata
  • KNXnet/IP
  • Modbus
  • OPC-UA
  • S7
@chrisdutz
Copy link
Contributor

I've just re-written the entire page .. thanks for reporting. Now the connection-pool page is no longer in the menu.

@in-fke
Copy link
Author

in-fke commented Feb 12, 2024

I've just re-written the entire page ..

Thanks for following up on this rather quickly.
Question remains: how to do "tear down" a connection pool, e.g. for shutdown / restart mechanisms.
We have a highly configurable framework and may need to "re-deploy" during runtime.

@chrisdutz
Copy link
Contributor

There currently is no such mechanism. Could I ask you to create a Feature-Request for this functionality?

@in-fke
Copy link
Author

in-fke commented Feb 12, 2024

There currently is no such mechanism. Could I ask you to create a Feature-Request for this functionality?

Sure, #1399

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants