Page 58 - ASBIRES-2017_Preceedings
P. 58
Alagalla & Arudchelvam
6.2 Limitation of the System access is a must. Therefore handling
concurrent access should be
Difficult to match sails ORM addressed in future modifications.
Concurrency issue was raised when
multiple users are trying to modify a 7 CONCLUSION
shared content at the same time. In this work a method to avoid storing
According to the users’ functionalities, the company’s email in to the spam folder of
only occasion it may happen is that clients’ email is successfully implemented
modifying the vacancy details of the and tested. In this method, Sails.JS backend
company because vacancy details can system and Google authentication system
be updated simultaneously by multiple are used. Further, time compatibility of the
users. But in the real world scenario, it receiver and sender are properly handled and
may happen very rarely. Apart from displayed in the email using Sails.JS ORM
that concurrency issues will not be REFERENCES
raised by other user functionalities.
Does not support offline access Pour, A.A., Kholghi, R., & Roudsari, S.B,
(2012). Minimizing the Time of Spam
6.3 Future Work of the System Mail Detection by Relocating Filtering
System to the Sender Mail Server.
Handle concurrent access: International Journal of Network Security
Even though concurrency problem is & Its Applications (IJNSA), 4(2).
not a critical issue at present, it will Rao J.M., & Reiley D.H. (2012).
be an issue with future enhancements. Economics of Spam. Journal of Economic
Basically in future, the system will Perspectives, 26(3), 87–110.
work with many internal systems. In
that case, handling concurrency
48
