Hi, I think i just found a new way of doing some crunching on computer not connected to the internet. Like probably many of you, my work computer is behing a proxy server. So i needed a computer acting as a send-n-receive server. The trick is packaging... Im working on a first version of a server and client side tool to do that. If your interested please post back on this so i would know if the effort is worth the pain ;)

Space the final frontier...will see about that Picard!

---

> Hi, I think i just found a new way of doing some crunching on computer not
> connected to the internet. Like probably many of you, my work computer is
> behing a proxy server. So i needed a computer acting as a send-n-receive
> server. The trick is packaging... Im working on a first version of a server
> and client side tool to do that. If your interested please post back on this
> so i would know if the effort is worth the pain ;)
>
> Space the final frontier...will see about that Picard!
>
Actually a queue is in the works for a future release.

---

Is it a connected to internet server - not connected client type of queue?

The little application im coding now works as follow:

1) Server (Connected to internet) sends request to client.
2) Client stop core service and package BOINC.
3) Client package BOINC.
4) Client sends package to server's FTP account.
5) Client wait for server's trigger.
6) Server unpack BOINC.
7) Server run core app therefore uploading and downloading WUs.
8) Server stop core app and package BOINC.
9) Server sends back BOINC package.
10) Client unpack BOINC and restart core app.

When will the release you'ved talk about be ready? Maybe my little app could be useful 'til the realease.

Regards.

Space the final frontier...will see about that Picard!

---

>
> When will the release you'ved talk about be ready? Maybe my little app could
> be useful 'til the realease.
>

Could be better than that. User contributed software often outshines the vanilla stuff provided. Just look at BOINCView vs BOINCMgr - one I use all the time, the other hasn't been opened for weeks; you guess which.

Good luck with it. Making processing available for off-line machines will will massively increase the number of potential hosts and participants.

PS.
Would this be for Windows only?

---

> Is it a connected to internet server - not connected client type of queue?
>
> The little application im coding now works as follow:
>
> 1) Server (Connected to internet) sends request to client.
> 2) Client stop core service and package BOINC.
> 3) Client package BOINC.
> 4) Client sends package to server's FTP account.
> 5) Client wait for server's trigger.
> 6) Server unpack BOINC.
> 7) Server run core app therefore uploading and downloading WUs.
> 8) Server stop core app and package BOINC.
> 9) Server sends back BOINC package.
> 10) Client unpack BOINC and restart core app.
>
> When will the release you'ved talk about be ready? Maybe my little app could
> be useful 'til the realease.
>
> Regards.
>
> Space the final frontier...will see about that Picard!
>
It was supposed to be here already but apparently isn't ready for prime time yet.

---

> >
> > When will the release you'ved talk about be ready? Maybe my little app
> could
> > be useful 'til the realease.
> >
>
> Could be better than that. User contributed software often outshines the
> vanilla stuff provided. Just look at BOINCView vs BOINCMgr - one I use all the
> time, the other hasn't been opened for weeks; you guess which.
>
> Good luck with it. Making processing available for off-line machines will will
> massively increase the number of potential hosts and participants.
>
> PS.
> Would this be for Windows only?
>
>

For now yes Windows only, but easyly applicable on other platforms.

---