Hi Thanasis, I took a look into the HttpListeners. >From a technical point, using this should be possible. But (*g*) in the end would incorporate re-coding quite some stuff regarding HTTP header handling etc. Is there any "advantage" of this simpleserver? More like "food for thoughts":
I gave a a sample implementation of the Status page a try with the Jersey/REST approach: https://github.com/derjust/smslib/commit/97d50a9e359b16fe9101db989509efe803a6b392 Isn't that different from the simpleserver one but provides more future flexibility regarding REST plus IMHO a more-known library? Filtering like the ACL I have also done in the SecurityFilter class in the same package. Yes I'm aware that REST endpoints are not usually made to return static resources like HTML pages - but the performance impact should be negligible. Yours, Sebastian -- You received this message because you are subscribed to the Google Groups "SMSLib Discussion Group" group. To view this discussion on the web visit https://groups.google.com/d/msgid/smslib/45068e1a-8a9c-4106-b530-1896e7dc21aa%40googlegroups.com.
