I'm currently toying with splitting up the hugely monolithic rx.c file into smaller files, with one file for each structure and function that's currently overloaded into rx.c (so rx_service.c, rx_conn.c, rx_call.c and so on). Before I do so, I'd be interested in hearing screams of pain from people who are currently maintaining external patch trees against rx, and who would be affected by such a code reorganisation.
Speak now or forever ... S. _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
