Servoy 2.2.1 Release Candidate 1

Classic Servoy
21

jaleman:
Because a batch processor is a servoy solution it’s very simple to build, maintain and debug.

Servoy Batch Processors: I like them!

Great work!
I already love them and I didn’t have sex with them yet… :D

22

jaleman:

  • Servers can run any amount of batch processors
  • Any solution can be a batch processor
  • ..simply by setting a startup method in it to do the batch…
  • .. then in the admin page tell the server it is the batch processor
  • that’s it
  • additionally: you can use the scheduler plugin in a solution to only run the ‘batch’ at certain times/intervals or: run in a loop to run continuously. If you run in a loop make sure to put in some sleep() statements once in a while to not use all cpu power of your hosting server.

Questions:

  1. Is it possible to call a method inside of a batch processor from a Servoy Client? I’m thinking about having a batch proc. sitting there and waiting for some client to give him orders, I’m thinking about duplicating large foundset when stored procedures are not an option (MySQL) or performing large server side export, DB to external web site sync, etc.

  2. I suppose that being an HC each batch processor will use one client license, am I right?

23
  1. create a queue. eg. in a table and have the hc check that table for instructions
  2. yes, each hc eats one license
24

It can be used in many many ways. To try it out I built a reminder system with it for a appointment system. It sends reminders to people by email or SMS (text on phone) a certain interval before an appointment. Very simple Servoy method does a find every minute on messages that are due for sending, sends them and marks them as sent. Built and tested in 15 minutes. I put it live 23 days ago and it has been running without a glitch.

25

jaleman:
Any solution can be a batch processor

It will be very interesting to hear how people use this. Remote backups using the headless client, reminder systems … I look forward to hearing ideas.

26

Westy:
It will be very interesting to hear how people use this. Remote backups using the headless client, reminder systems … I look forward to hearing ideas.

Send queued data to another system that is not online all the time.

Another way to handle transactions: Post-process records that were not available (e.g., were locked) at the time a routine was run.

Write lines of text coming in from a method run by various clients to a single document.

umm…

kazar